Also, I have yet to see a purely technological decision of that magnitude, even in the world of compilers.
I see Rubinius and JRuby winning the race, but I don't see any of them _replacing_ MRI.
Also, I have yet to see a purely technological decision of that magnitude, even in the world of compilers.
I see Rubinius and JRuby winning the race, but I don't see any of them _replacing_ MRI.
I understand there are good reasons to keep MRI around, but the idea of making Rubinius the future of core Ruby development is not an outlandish idea.
(note: I'm not following MacRuby Development very closely at the moment.)
One of the big things about the new VM is that it eliminates the global interpreter lock, meaning MacRuby probably has much better parallelization than MRI. With the VM alone I think they are on their way to being their own Ruby implementation.
All of this is a bit disappointing considering that they could have shared their improvements upstream and improved MRI performance for everyone, not just for Mac apps.