Also, this could be an interesting read: http://www.engineyard.com/blog/2010/making-ruby-fast-the-rub...
Also, this could be an interesting read: http://www.engineyard.com/blog/2010/making-ruby-fast-the-rub...
I would think that the metaprogramming features of ruby which make it so much fun would also make it n times harder to build a JIT for.
Here is the current status towards 1.9 implementation: http://status.rubini.us/
From the frontpage:
"How compatible is Rubinius? From the start, compatibility has been critical to us. To that end, we created the RubySpec to ensure that we maintained parity with official Ruby. We are currently at a 93% RubySpec pass rate and growing everyday. For now Rubinius is targeting MRI 1.8.7 (1.9 is on the post 1.0 list). Most Gems, Rails plugins and C-Extensions work right out of the box. If you find a bug, let us know and we'll get on top of it."