4 ms·
Things are changing on this front. We now have better fibres for IO bound code and ractors for thread safe CPU bound code. Personally I don’t think ractors ar
by Lio 5y ago
Things are changing on this front.
We now have better fibres for IO bound code and ractors for thread safe CPU bound code.
Personally I don’t think ractors are completely solid but I don’t think it will long until they are.
I think Ruby’s future is pretty rosey compared to a few years ago.
I would even say that small projects can avoid Sidekiq and Redis by using Good Job and Postgres making them even cheaper to start with.
- pizza234 5y agoRegarding the ractors, I'm a big fan - I believe true multithreading in a language with a GIL is a revolutionary change. On the other hand, I also believe that Ruby has always had a culture of single threading, so for the ecosystem to adjust (in practice, for having threadsafe libraries), it will take a very long time (if ever; I'm pessimitic and personally believe the ecosystem will never catch up, but of course, I wish all the best :)).