In a recent talk in Amsterdam Koichi said that Matz has very high ambitions for Ruby 3. They will focus on concurrency and it is expected that the concurrency i

In a recent talk in Amsterdam Koichi said that Matz has very high ambitions for Ruby 3. They will focus on concurrency and it is expected that the concurrency interface might dramatically change. 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.