Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

You can also use jruby now. I'm not trying to diminish rubinius, I hope it works out well and I worked with one of the contributors, but I've been using jruby for a while now and it's great.

Re: Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

#5

Post by poet » Thu, Feb 17, 2011, 8:39 PM UTC

Beautiful example how a combination of open source enthusiasm and commercial interest can generate some first class software. There's no way this could have happened without Evan's initial enthusiasm or Engine Yard's support. TBH I can list off dozens of open source projects that are one sponsor away from another level greatness. :P

Re: Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

#6

Post by glenjamin » Thu, Feb 17, 2011, 8:40 PM UTC

I've never been massively keen on the carious implementations of ruby, they're all a bit different and those differences appear to be documented poorly. This is most visible if compared to the python landscape.

Re: Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

#7

Post by updog » Thu, Feb 17, 2011, 8:49 PM UTC

poet wrote: post #5

Beautiful example how a combination of open source enthusiasm and commercial interest can generate some first class software. There's no way this could have happened without Evan's initial enthusiasm or Engine Yard's support. TBH I can list off dozens of open source projects that are one sponsor away from another level greatness. :P

You mean, can generate some plans for some first class software. ;)

Re: Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

#8

Post by tedunangst » Thu, Feb 17, 2011, 8:58 PM UTC

glenjamin wrote: post #6

I've never been massively keen on the carious implementations of ruby, they're all a bit different and those differences appear to be documented poorly. This is most visible if compared to the python landscape.

I'm afraid that the only explanation I can formulate for your comment is that you are simply unaware of alternative python implementations, because the differences between rubies and pythons are documented approximately evenly.

Re: Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

#9

Post by tierack » Thu, Feb 17, 2011, 9:01 PM UTC

glenjamin wrote: post #6

I've never been massively keen on the carious implementations of ruby, they're all a bit different and those differences appear to be documented poorly. This is most visible if compared to the python landscape.

I don't have a handle on the Python implementation landscape, but the various Rubies all regularly contribute to rubyspec[0] and report on how they're doing. And with rvm[1] it's incredibly easy to test code across rubies. From where I'm sitting, it seems dead simple to find the differences and how they could affect me.

0: https://github.com/rubyspec/rubyspec 1: http://rvm.beginrescueend.com/

Re: Rubinius Announces Plans for GIL Elimination, JIT Improvements, Targetable VM

#10

Post by ekidd » Thu, Feb 17, 2011, 9:23 PM UTC

This is really great news: I spent some time digging around in the Rubinius JIT in December, and realized that it wasn't going to generate significantly better code until the byte codes were replaced with an intermediate representation that made type checks visible to the optimizer.

In the long run, Ruby implementations will be at least 1 order of magnitude faster than either MRI 1.9 or JRuby. And I'm glad to see that the Rubinius folks are taking the necessary steps to get there.