Second Draft: Coroutines

[Jin]

On Wednesday, 15 January 2025 at 16:19:37 UTC, Richard (Rikki) 
Andrew Cattermole wrote:
> Ask Adam all about how much hell it was to do in C# before they 
> added async/await

I note that with the advent of async/await in JS, development for 
the browser turned into hell. And when node-fibers (a native 
nodejs extension that adds support for coroutines with a stack at 
runtime) was broken, all hell broke loose on the servers. Briefly 
about async/await problems:

- [Low performance due to the inability to properly optimize the 
code.](https://page.hyoo.ru/#!=btunlj_fp1tum/View'btunlj_fp1tum'.Details=%D0%90%D1%81%D0%B8%D0%BD%D1%85%D1%80%D0%BE%D0%BD%D0%BD%D1%8B%D0%B9%20%D0%BA%D0%B5%D0%B9%D1%81)
- [Different colors of functions that virally affect the call 
stack.](https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/)
- [Inability to abort a deep subtasks without manually drawing a 
CancellationToken since await is not 
owning.](https://hackernoon.com/why-do-you-need-a-cancellation-token-in-c-for-tasks)
- [The need to reinvent the stack as an 
AsyncContext.](https://github.com/tc39/proposal-async-context)