<@U0ZFBBUBU> I can recommend this piece on why asy...
# coroutines
e
@groostav I can recommend this piece on why async has to be always async. It is about callbacks, but it applies to any style of async programming: https://blog.ometer.com/2011/07/24/callbacks-synchronous-and-asynchronous/
🤔 1
g
elizarov: Thanks for this, I think ill buy what you guys are selling here but I confess in an ideal message&coroutine-based (lockless) world I feel like having this eager dispatch is a good idea. But then, with lock-heavy data-bases and lock-heavy UI frameworks I suppose that'l never happen.