I'm surprized there's not a PyPy version of Ruby. _why's unholy showed it's trivial to compile Ruby into Python (in many cases). It shouldn't be too hard (famous last words) to make a Ruby VM with PyPy. If they don't like the idea, they could make a RPython <-> RRuby translator, and port the whole thing to RRuby.
Yes, I've heard about Rubinous (the Ruby equivalent to PyPy), but it doesn't have the resources.
If anyone feels like paying my salary for a year, I'd love to work on this project ;) Not surprisingly, at the moment most (all?) of the PyPy developers are Python people, so none of us have invested time into a Ruby VM in our spare time, but it's definitely a cool project.
> _why's unholy showed it's trivial to compile Ruby into Python (in many cases). It shouldn't be too hard (famous last words) to make a Ruby VM with PyPy.
Basic structures like if, else, while etc. is easy. The hard part is the object model (including constant lookup) and long jumps (exceptions, next/break). Let's not forget the big core library which you need to implement if you want it to be usable at all…
Maybe because there's already a ton of working ruby implementations that all have their own sets of advantages. There's rubinous (which you named), they seem to be making pretty nice progress, there's mri, ree, maglev, macruby, ironruby and finally there's jruby which is actually often the fastest ruby interpreter around.
It came a bit as a surprise to me that the author mentions jython as an example that languages on the hotspot vm don't benefit too much from its features - jruby certainly does.