3 ms·
concurrency will always limit ruby.. it will never ever get there and that's ok because that's not ruby's goal.
by tmat 9y ago
concurrency will always limit ruby.. it will never ever get there and that's ok because that's not ruby's goal.
- lloeki 9y agoRuby (MRI) is perfectly concurrent already, it just sucks at parallelism.
- astrodust 9y agoRuby has some of the best concurrency support: Fibers and threads are all well-established features. JRuby and Rubinius can handle native threads, no Global Interpreter Lock (GIL) at all. The downside is most Ruby code bases are reluctant to take advantage of it, or even be thread-safe or fiber-aware, which can make writing apps more challenging than an environment like Node.js where there's established standards and expectations.
- MrBra 9y agoAlso let's not forget about Guilds... http://olivierlacan.com/posts/concurrency-in-ruby-3-with-guilds/ http://olivierlacan.com/posts/concurrency-in-ruby-3-with-gui...