> Guess what kind of "interpreter" most people would need? The async/await kind. Because we never got the chance to explore the full power of generators, and w

> Guess what kind of "interpreter" most people would need? The async/await kind. Because we never got the chance to explore the full power of generators, and we probably never will because of it. We will of course solve our other problems the usual old-fashioned way (e.g. DI for transactions, some other funky mechanisms for CLS, no automatic SQL query optimizations, no automatic GraphQL query optimizations). You can't need what you aren't aware of. > The argument here is against a core language feature and has nothing to do with async/await. Not directly, no, but thanks to async/await a lot more errors will be flying up the call stack than ever before. This will greatly increase the chances that you catch something you didn't intend to catch. Unless you have filtered catch, which would improve that a little bit.