RubyInstaller has an RC2 version of Ruby 1.8.7-p249.
Base installation is a snap. Click download, run, next, click accept, next, click “Add Ruby executables to your PATH”, install, finish.
This currently comes with RubyGems 1.3.5. RubyGems 1.3.6 is out and contains a fix that makes it easier to install the Rails beta, so:
gem update --system
This will cause warnings later, which can be avoided by doing the following:
gem uninstall rubygems-update
Next, to install sqlite3, download and unzip both precompiled binaries for Windows for the command-line and DLL without the TCL bindings, exploded the zip files, and copy the results to you C:\ruby\bin directory. The result should look something like this:
@ECHO OFF
IF NOT "%~f0" == "~f0" GOTO :WinNT
@"ruby.exe" "script/rails" %1 %2 %3 %4 %5 %6 %7 %8 %9
GOTO :EOF
:WinNT
@"ruby.exe" "script/rails" %*
Once this was complete, the initial test results look pretty good. The only error reported in this test has to do with the automation of the execution of irb from my script, and not a failure with Ruby or Rails itself.
Tim Bray: Any standard that tries to constrain the way in which data, once received, is processed, is broken.
HTML5 is clearly broken by Tim’s definition. And while it may go too far in places, I can say that there are definitely many areas where that definition is a good thing. I wouldn’t have agreed with that statement a few years ago, but I do now. Enthusiastically. But to explain why, I need to first back up.
At no time did the current, up to the minute, versions — complete with occasional typos and botched commits — of the editor’s drafts become unavailable: HTML5, RDFa, MicroData, 2D Context, Markup, Diffs.
The absolute most that anybody, anywhere, ever proposed was that these very same documents be published with different labels
A few things that you can be sure of. The format of the presentation will be HTML5. And that it will be made available either on the web either concurrent with, or shortly after, the presentation itself.
DeWitt Clinton: The idea is that someday, any host on the web should be able to implement these open protocols and send messages back and forth in real time with users from any network, without any one company in the middle. The web contains the social graph, the protocols are standard web protocols, the messages can contain whatever crazy stuff people think to put in them.
DeWitt posted this within Buzz. If I want to keep up with things DeWitt’s posts via buzz, there’s a feed for that. This particular post generated a lot of comments, and there is a feed for that. I do have someissues I would like to see addressed, but basically what this means that Google just made available a blog to every GMail user.
Simon Phipps: While Matthew’s discussion is good (and the links are very useful), he misses the key point: that communities where one member has significantly more rights than all the rest tend to fail. If you must aggregate copyright, share rather than transfer, and aggregate in the hands of a community-controlled entity.
Tim Bray: the Net is the greatest listening engine ever devised. These days anyone can choose, with its help, to be well-informed
Yehuda Katz: It’s easy to spit out “lmgtfy.com” or RTFM, but in truth, these beginners barely know where to look. All too often, we (open source leaders) assume that if someone couldn’t figure out the right search term on Google, they can never become a viable community member.
I claim that there is a third ingredient that makes this all work. That ingredient is participating.
Anthony Laforge: The Dev channel has been updated to 5.0.317.0 for Google Chrome Frame.
This release addresses the issue I reported in September. Accordingly, I have set these pages to opt-in to the use of Google Chrome Frame if the User Agent header indicates that this is supported.
David Heinemeier Hansson: You thought we were never going to get to this day, didn’t you? Ye of little faith. Because here is the first real, public release of Rails 3.0 in the form of a beta package that we’ve toiled long and hard over. It’s surely not perfect yet, but we were out of blockers on the list, so here we go. Please give it a run around the block, try to update some old applications, try to start some new ones, and report back all the issues you find.
Rails 3.0 requires 1.8.7 or later. Both InstantRails and the (current, released) version of RubyInstaller bundle Ruby 1.8.6. The files on the Ruby site seem to be a scavenger hunt. While the next release of RubyInstaller will address this, we can run today with Cygwin.