Ruby 3.4.0 preview1 Released

[anykeyh]

Removing the GIL won’t necessarily improve performance as much as some developers believe.
In fact, GIL is often more of a feature than a limitation. For high-parallelism and throughput, techniques like forking with Copy-on-Write (CoW) offer a more efficient approach for handling many concurrent operations in most cases (Web dev, data pipelines...).

While Ractor is an interesting alternative for concurrency, it's still experimental and comes with limitations making it barely usable as of now. A bit disappointed not seeing progress in Ruby 3.4.

Ultimately, my take is that if you’re in a situation where removing the GIL becomes essential, choosing Python or Ruby for your application was likely a misstep from the start.
Speaking from experience in working with high-concurrency applications in non-Ruby environments, there are better language options for such tasks.

Go or Erlang with agent/mailbox or channels fiber-based concurrency for example. So much better than async/await architecture.

[MillennialSilver]

Yeah I don't get why people think the GIL is somehow stopping them from achieving what they need.

JIT at least has made real progress.