ioquatix (Samuel Williams, the author) is doing tons of great work for Ruby at the moment. You'll want to check out, for instance:<p>- <a href="https://github.com/socketry/async" rel="nofollow">https://github.com/socketry/async</a> "An awesome asynchronous event-driven reactor for Ruby"<p>- <a href="https://github.com/socketry/falcon" rel="nofollow">https://github.com/socketry/falcon</a> "A high-performance web server for Ruby, supporting HTTP/1, HTTP/2 and TLS"<p>I can recommend following him on twitter too: <a href="http://twitter.com/ioquatix" rel="nofollow">http://twitter.com/ioquatix</a>
I've run into an issue where a Ruby library is technically thread-safe but there is some C library code that blocks (i.e. connect with TinyTds). This makes it practically unusable with threading under special scenarios where your SQL servers are not guaranteed to be available.
I haven't touched Ruby in a while, but are there any common multithreaded use cases? It seemed like the direction was to go multi-process for web workloads (E.g. with Unicorn).
Working complex systems develop from working simple systems. This is trying to get a working complex system by creating another initial working complex system. If only ruby didn't have that darned assignment operator...