Ideas for Improving Ruby During Google Summer of Code 2015
github.com
github.com
With that in mind I'd say that removing the GIL is a rather useless effort. It would probably not do much for performance and most likely result in many very buggy releases of Ruby possibly tarnishing its reputation for reliability.
Imagine instead if Ruby 3 had an actor system like celluloid integrated to the core, and it would require any globally defined objects (I.e. most classes and modules) to be actors. (Perhaps by making the default class parent be ActorObject, instead of Object or something) That would in one fell swoop deal with concurrency, while retaining the clean feel of Ruby.
But Just when should we expect Ruby 3.0? 2020?
On Wikipedia: >Since YARV has become the official Ruby interpreter for Ruby 1.9, it is also named KRI (Koichi's Ruby Interpreter), in the same vein as the original Ruby MRI, named for Ruby's creator Yukihiro Matsumoto.
So is one of them wrong? I'm confused.
>MRI executes Ruby via an interpreted stack-machine bytecode language known as YARV (Yet Another Ruby VM) bytecode.
So YARV is a Ruby VM that has instructions and bytecode. Are you still confused?
On the other hand, to tell the "default" ruby apart from jruby and rubinius, one might still refer to it as "MRI". Also, Robert Metcalfe once said something to the effect that "Ethernet cannot die - if something comes along to replace it, it will just be called Ethernet" or something along those lines. Maybe something similar is at work here? (Sloppiness is more likely, though.)