rubinius

That means that Rubinius might finally become a real alternative to MRI.

Indeed it's becoming quite promising (using crystal already for few pet scripts which were too slow even for rubinius).

Unlike some other Ruby implementations, Rubinius also intends to be compatible with C extensions written for MRI.

Besides, let's be honest -- Python ain't that much faster than Ruby, especially with Rubinius et al on the horizon.

This would have been really useful when projects like JRuby and Rubinius were earlier along.

Merb just might get a boost and EY now employs (at least) 4 Rubinius developers.

I'm not a huge fan of Ruby, but Ruby, its community, and rubinius are doing it much better.

I don't think PyPy or Rubinius have had anything close to the same level of investment.

If Rubinius doesn't blow all the others out of the water I'll be surprised.

It would be MRI if rubinius controls the project.

The Rubinius team's complaints (though hyperbolic) still stand.

I didn't realise that Rubinius and Merb were Engine Yard projects.

Rubinius matters because it "feels more joyful" when you know you can't do better by writing in C?

On the other hand, to tell the "default" ruby apart from jruby and rubinius, one might still refer to it as "MRI".

My understanding is that the standard will largely be compliant with RubySpec, pioneered by Rubinius.

Rubinius doesn't want to join is not because they don't want to invest the effort, they actually invested a lot of efforts before.

His 20% time project at Powerset is contributing to Rubinius.