it just listed the ways you can handle concurrency and parallelism in ruby 3 and what they each do.
Aka Threads which are backed by OS threads but are limited by the GIL when it comes to parallelism.
Fibers which are green threads aka windows 3 style concurrency.
Forking Processes.
and Ractor which is backed by a thread pool and offers real parallelism.
I would say that fibers, when used with Samuel’s ecosystem of gems act as node’s event loop (which I am guessing more people on here would be familiar with). They can auto switch on I/O like Ruby’s threads if you’re using a new enough version of Ruby.
Cool, thanks! Always curious to hear if there's something new out there.
I have always enjoyed using the BEAM ecosystem for concurrency, but Ruby has so much code and is great for "getting stuff done", so it's mostly what I keep using.
Aka Threads which are backed by OS threads but are limited by the GIL when it comes to parallelism. Fibers which are green threads aka windows 3 style concurrency. Forking Processes. and Ractor which is backed by a thread pool and offers real parallelism.