> Writing real multithreaded code without a GIL is hard. A GIL doesn't help developers. It only keeps the internal state of the VM consistent. You still need t

> Writing real multithreaded code without a GIL is hard. A GIL doesn't help developers. It only keeps the internal state of the VM consistent. You still need to to use locks, thread safe collections etc. That's one major reason why some people feel that OS threads + GIL is a poor trade-off. https://github.com/ruby-concurrency/concurrent-ruby#thread-safety https://github.com/ruby-concurrency/concurrent-ruby#thread-s...