News for hackers. Stuff that matters.
Re:Ruby has been fast enough for 13 years by chrisseaton on Monday May 16, 2016 @02:23PM (#11708377)
I'm not sure there are any realistic ideas to actually achieve this for MRI though (beyond the one-sentence bullet points in that article). The roadmap needs to have some roads on it rather than just wilderness!

That's speaking as someone who works full time on optimising Ruby, and wrote a PhD on it.

I think the one hope is that Evan Phoenix suggested an idea that would let an LLVM JIT optimise through the Ruby implementation, but this is a full-on research project (he said it wasn't, I'm not sure I agree), and nobody is working on it.

Re:Ruby has been fast enough for 13 years by MrBra on Thursday May 19, 2016 @02:09PM (#11732277)
You should watch the Evan Phoenix talk at RubyKaigi 2015 ("Ruby 2020") https://www.youtube.com/watch?v=QaLvtNpoc5o.

It proposes a very interesting path for Ruby to get way faster, without resorting to the JRuby implementation.

Basically what he's proposing is we could compile all the Ruby Stdlib ahead of time to a LLVM kind of bytecode. Once you do that, a JIT compiler for Ruby code could perform a way deeper optimization, because the compiler horizon-line will be stretched much further away: the compiler will be able to inspect the Stdlib bytecode and make optimizations to your Ruby code taking all that into account!

This could be a revolutionary approach for MRI, please go see the talk, it's really interesting!

Re:Ruby has been fast enough for 13 years by Freaky on Monday May 16, 2016 @03:13PM (#11708807)
Re:Ruby has been fast enough for 13 years by kristianp on Tuesday May 17, 2016 @12:07AM (#11711291)
How is GraalVM + JRubyTruffle going? It's a fast implementation of ruby.

https://github.com/graalvm/jrubytruffle