6 ms·
My belief is that lack of concurrency primitives is what will kill Ruby, not today, 10 years from now. We're running on momentum alone at this point. That said
by whistlerbrk 10y ago
My belief is that lack of concurrency primitives is what will kill Ruby, not today, 10 years from now. We're running on momentum alone at this point.
That said every Rubyist should be following Chris Seaton's work chrisseaton.com/rubytruffle/deoptimizing/ with JRuby Truffle+Graal. This is our best change, imo of course, to make Ruby fast.
- MrBra 10y agoYou should watch the Evan Phoenix talk at RubyKaigi 2015 ("Ruby 2020") https://www.youtube.com/watch?v=QaLvtNpoc5o 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!