The main argument is that you know what may block. But maybe it is the same as checked exceptions in Java? In a modern system everything may block and everything may raise lots of exceptions. It’s impossible to micromanage both - you need to pin them down on architectural level.
Async/await is strictly worse than green threads, except that the latter might require runtime and/or ABI changes that you cannot push out, whereas async is front-end sugar mostly hiding the fact that you're passing callbacks to enable "single-stack green threading." Am I wrong?
-
-
-
This is also the main argument against async/await. This is like having to annotate functions using floats or files - very interesting info but there goes seamless composability
End of conversation
New conversation -
-
-
גמרת אותי פה.
-
Come to Israel, I'll explain
End of conversation
New conversation -
-
-
It depends on what you count as "green threads" -- generating state machines directly can certainly be more efficient than stack switching.
-
An async call chain has to cost more than a setjmp at the innermost call, though we're talking peanuts either way
- 3 more replies
New conversation -
-
-
Sounds pretty much on point [shameless plug: http://eli.thegreenplace.net/2018/concurrent-servers-part-6-callbacks-promises-and-asyncawait/ …]
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
This Tweet is unavailable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.