Last week in Denver, the Rubinius guys had a coding sprint; read about it in Brian Ford’s Rubinius sprint retrospective and Wilson Bilkovich’s Implementing define_method. We at Sun supported it by covering the travel costs (well, we will as soon as I get the paperwork, guys) and by sending Charles Nutter along for a day. Looks like they got some good stuff done. Rubinius is an attempt to build the next-gen Ruby implementation. Which is happening in parallel with the “official” Ruby 1.9 work in Japan and the JRuby project. [Update: Pat Eyler interviews the sprinters.]
Basically, we’re supporting all of them. Along with giving Rubinius a hand, we employ half the JRuby committers, we’ve donated a server to Matz’s gang, and (I hope to be able to announce soon) we’re going to be giving the Japanese side some other support.
Why are we doing this? Because, in my view, Ruby isn’t finished. It’s a great substrate for Rails, it’s immensely useful for building all sorts of things, but it’s not fast enough. I agree with Avi Bryant’s argument that a language isn’t finished until it’s fast enough to extend itself. Frankly, none of the language enhancements proposed for Ruby 2.0 make my heart go pitter-patter. But give me a Ruby with performance as good as a really good Smalltalk VM, and the space of things for which you need statically-typed languages shrinks to a really uninteresting size.
Except for, nobody including me is smart enough to predict which of the Ruby.next implementations is going to have that performance mojo. So, it seems like the only reasonable thing is to bet on all of ’em. One thing that makes this easy is that all the teams get along with each other; a natural outgrowth of Ruby culture, and something from which we can all learn.
Contributions
Comment feed for ongoing:
From: Janne (Sep 21 2007, at 16:54)
I don't know; really seamless handling of text no matter what encoding certainly registers a flutter or two for me.
Speed is actually less of an issue, though it would be nice if it were addressed. For any really heavy lifting I'd just call out to components written in C/C++ or Matlab/Octave anyhow.
[link]
From: Wilson Bilkovich (Sep 22 2007, at 14:27)
Thanks again for sponsoring the sprint.
I'll get those forms in the mail ASAP. :)
Rubinius is out there. It can't be bargained with. It can't be reasoned with. It doesn't feel pity, or remorse, or fear. And it absolutely will not stop, ever, until you are dead.
I mean, umm.. untl it is the premier Ruby implementation.
[link]
From: Steven (Sep 25 2007, at 12:14)
Wow, more good being done by Sun. Would now be a good time to start hinting that they should build with compilers other than GCC?
[link]