3 ms·

Thread support in interpreted languages isn’t that parallel to begin with.

• jashmatthews 8y ago
  JRuby threads are fully parallel and in production use today. CRuby's GIL is an implementation choice rather a property of dynamic/interpreted languages.
  • buckysock 8y ago
    I’m wondering.. what is the effect of letting the JVM handle synchronization then ? Wouldn’t they still need to synchronize within JvM ?
  • viraptor 8y ago
    Is it really a "choice" if the alternative is really hard to achieve in practice? It's like calling python's GIL a choice... with numerous projects trying to get rid of it in various ways and never really succeeding to do it while keeping the single threaded performance and the extensions API.
    • pjmlp 8y ago
      It is a choice to keep backwards compatibility with the C extensions API. The GIL would be quite easy to replace otherwise.
      • jashmatthews 8y ago
        > It is a choice to keep backwards compatibility with the C extensions API. IIUC for CRuby it's mostly about how to keep the VM simple. Koichi Sasada is working on an ownership based model like Erlang has, which sidesteps a bunch of theses issues.