> What you are describing is really “async-never.” And in fact, the programming model that async/await gives you is in fact, blocking. To the programmer, awaiti

> What you are describing is really “async-never.” And in fact, the programming model that async/await gives you is in fact, blocking. To the programmer, awaiting is no different from blocking a function. Not exactly, I rather proposed async calls are explicit, instead of blocking calls being explicit. Most people have no problem with the APPEARANCE of blocking. They mind if it's actually blocking under the hood. It's normal that when you issue some HTTP request, for ex. you can't proceed processing the response until you get it. One way or another "you await" that moment. Regarding whether it's free or not, I still don't quite understand the problem TBH. An event loop isn't a hard addition to any language. The only thing I wonder about is stack fragmentation.