I had the pleasure of listening to Samuel Williams present his ideas at a Ruby meetup a few months ago….
…I think he is on to something.
If you have ever tried to weld libraries together, you will know that getting the concurrency behaviours to “play nice” with other libraries is one of the hard parts. ie. His drive to make async behaviour composable is spot on.
I had the pleasure of listening to Samuel Williams present his ideas at a Ruby meetup a few months ago….
…I think he is on to something.
If you have ever tried to weld libraries together, you will know that getting the concurrency behaviours to “play nice” with other libraries is one of the hard parts. ie. His drive to make async behaviour composable is spot on.
We need it.
While that post is certainly interesting, I believe what he is saying here… https://www.codeotaku.com/journal/2018-06/improving-ruby-concurrency/index and doing https://github.com/socketry/async/tree/master/lib/async are more compelling.
I’ve tried threads and promise like systems and reactor like systems and…. I’m not happy.
I need to take a bit more time to play with his Async library. It looks really promising.