A couple new commands in Try Ruby!

• help #: Hop between chapters by using the summary number. Try it: help 1, help 2, wtf? 3, etc.
• reset: Throws a RubyLex::TerminateLineInput if you get nested too deeply and all you see is the double dot prompt.

A Safari fix is on its way. Sit tight.

Ctrl-D will now also do a reset. If that’s more comfortable for you. I’m trying to keep light on the keybindings which interfere with the browser—still, do any others make sense?

So, Try Ruby has been riddled with problems. At about 9 AM EST yesterday the whole thing was swapping pretty heavily. This was right in the epicenter of the Digg stampede. I mean imagine trying to manage all these hundreds of Ruby processes opening up. CPU is fine, but a single Ruby process will gobble up a good share of memory lickety split.

Continue to full post. (280 words)

You hear that sound? That subtle squeak which instantly reminds one of distant ducks quacking great spools of wood grain? Yeah, that one. That’s what it sounds like when the world gets together to code.

Matz spilled the cat two days ago on his blog, as one of the many testers I employed to shake apart my new Try Ruby online tutorial. I ran this sucker by the #hoodwinkd crew, the project.ioni.sts and the #rubyist.org gang, Florian Gross, and even the illustrious Guy Decoux. A very capable lot, I thank them all.

So, 205,000 lines of Ruby code in two days. I’m watching all this code come in and finding myself very entertained. Here’s a few of my favorite moments.

Continue to full post. (326 words)