[stefanchrobot]

A much better suggestion would be to look for a language/VM that supports a better concurrency primitives, like Elixir/Erlang. Obviously you can't run that everywhere, so sometimes you'd have to deal with threads. But after giving Ruby an honest shot at writing a backend system and hitting concurrency bugs (in an external gem), I'd rather avoid threaded programming model altogether.

[jpz]

This is another categorical statement. I love how the languages you mention do concurrency, but I don't think that if you use threads, one should only be doing it in Elixir/Erlang (or go).

I find that nearly as disagreeable as the original posting.

[stefanchrobot]

I'm categorical only in terms of my personal preferences. Threading model is just hard, so in general, I'd suggest looking for alternatives. But that's not a universal advice as there are cases where it does not apply or the developers are up to the task of handling multiple threads.