4 ms·

For a lot of folks, rubinius has already replaced MRI. At least locally while developing. I am not sure, why you are saying "It will never happen".

by gnufied 15y ago

Xylakant 15y ago
> For a lot of folks, rubinius has already replaced MRI. At least locally while developing. This in itself certainly is a great achievement for the rubinius team and one to be proud of. However, I personally have to see a large production deployment. I consider rbx a serious alternative to mri, just as jruby is a serious alternative. I'll call it "replacement" once heroku starts using rbx and drops mri support. I don't see that happening in the next couple of years, there's just way too much investment behind mri for it to just go away.
- regularfry 15y ago
  I think we're going to see a fork in the community, and I think heroku will end up supporting both MRI and rbx as equals.
  - Xylakant 15y ago
    I don't think we'll see a fork. There will be some gems that support rbx only and some that are MRI only and some that require jruby. However, seeing how things go with jruby I'd expect that most of the code stays runtime agnostic and people will use whatever runtime suits the current problem best. Given that there's a ruby spec now I imagine we'll end up pretty much where javascript is: Multiple runtimes that all support pretty much the same code. Or have a look at java or c, there's more than one jvm and with good reason as well as multiple c compilers that all produce working code :) And yes, I do see heroku supporting both MRI and rbx as equals, but my point was that that's not replacing.
Argorak 15y ago
Thats the user perspective. I don't see the MRI team, which has built a whole tool-chain around developing MRI throwing away all that and to switch to a new platform. I like Rubinius very much, as I do with JRuby, I just don't see Rubinius replacing MRI. Thats what I meant by 'dreaming'. A non-realistic expectation that is not backed by any real events.
- regularfry 15y ago
  Outside the MRI team, what the MRI team get up to only matters as long as the community pays attention to them. If everyone decided to switch en masse to Rubinius, MRI might not go away, but it would definitely be sidelined into irrelevance.

For a lot of folks, rubinius has already replaced MRI. At least locally while developing. I am not sure, why you are saying "It will never happen".

by gnufied 15y ago

For a lot of folks, rubinius has already replaced MRI. At least locally while developing. I am not sure, why you are saying "It will never happen".

Xylakant 15y ago

> For a lot of folks, rubinius has already replaced MRI. At least locally while developing. This in itself certainly is a great achievement for the rubinius team and one to be proud of. However, I personally have to see a large production deployment. I consider rbx a serious alternative to mri, just as jruby is a serious alternative. I'll call it "replacement" once heroku starts using rbx and drops mri support. I don't see that happening in the next couple of years, there's just way too much investment behind mri for it to just go away.

regularfry 15y ago
I think we're going to see a fork in the community, and I think heroku will end up supporting both MRI and rbx as equals.
- Xylakant 15y ago
  I don't think we'll see a fork. There will be some gems that support rbx only and some that are MRI only and some that require jruby. However, seeing how things go with jruby I'd expect that most of the code stays runtime agnostic and people will use whatever runtime suits the current problem best. Given that there's a ruby spec now I imagine we'll end up pretty much where javascript is: Multiple runtimes that all support pretty much the same code. Or have a look at java or c, there's more than one jvm and with good reason as well as multiple c compilers that all produce working code :) And yes, I do see heroku supporting both MRI and rbx as equals, but my point was that that's not replacing.

Argorak 15y ago

Thats the user perspective. I don't see the MRI team, which has built a whole tool-chain around developing MRI throwing away all that and to switch to a new platform. I like Rubinius very much, as I do with JRuby, I just don't see Rubinius replacing MRI. Thats what I meant by 'dreaming'. A non-realistic expectation that is not backed by any real events.

regularfry 15y ago
Outside the MRI team, what the MRI team get up to only matters as long as the community pays attention to them. If everyone decided to switch en masse to Rubinius, MRI might not go away, but it would definitely be sidelined into irrelevance.