Post #3788881

@zwol@masto.hackers.town Asynchronous brings its own problems. Priority inheritance is hard to propagate at any time other than 'this queue us full' time, so you will end up in bursty situations. Getting low latency is painful (high throughput is relatively easy). If you want to expose remote services to other languages, you are probably in a better state now than 20 years ago because a lot have some notion of async, but most code wants to operate with synchronous APIs. And handling errors becomes really exciting: everything now needs to be a continuation that takes a failure and a success case.