> Rubinius and PyPy take quite different approaches to solving the same general problem. > However, it's not breaking new ground like PyPy is. I know about th

> Rubinius and PyPy take quite different approaches to solving the same general problem. > However, it's not breaking new ground like PyPy is. I know about the differences. My response was to the parent post "if there is something like PyPy for Ruby". Rubinius doesn't need to break new grounds, nor provide a toolset for implementing interpreters. All it needs to do is to provide a decent JIT with reasonable speed and low memory consumption, with the added benefit of large parts of it in Ruby, so that the contribution ecosystem is more active. That will be pretty much analogous(and all analogies, by definition, are inexact. Or else they won't be called ananlogy) to what PyPy is for Pythonistas.