> Anyways, if async functions are so good, why not have all functions async? They aren't. They're only good when the primary thing that the function is doing i

> Anyways, if async functions are so good, why not have all functions async? They aren't. They're only good when the primary thing that the function is doing is waiting. > When my code is called by a 3rd party library, I can not change my code to async. That's the most unpleasant property of today's async / await. What yesterday was quick computation tomorrow can become a network call. You can still do that. Network calls don't have to be async. Blocking network calls still exist, just as they did before async was created. > Hopefully, compilers of the future will be able to automatically parallelize computations. Ah, yes, the famous sufficiently smart computer that can determine if two operations happening on the other side of the network depend on each other or not. Personally, I'm not holding my breath.