3 ms·
> CRuby has the disadvantage of a global interpreter lock. This means that parallelism can only be achieved via multiple processes. Even for Ruby code (and not
by dragonwriter 3y ago
> CRuby has the disadvantage of a global interpreter lock. This means that parallelism can only be achieved via multiple processes.
Even for Ruby code (and not native code running in a Ruby app) this is false since the introduction of Ractors, which are units within a single process that communicate without shared mutable (user) state, as the GVL is only “global” to a Ractor, not a process.
(Also worth noting, given the broader topic here, that Ruby has an available async implementation built on top of fibers which doesn't rely on special syntax and allows code to be blocking or non-blocking depending on context.)