> Do people use coroutines? Yes, but not in production code.
Now I'm wondering if I'm the one who's confused. Either the author has also never heard of Go or goroutines don't meet his/her definition of coroutines.
When terms move from academia into common usage, they inevitably blur. Academia had a specific definition of coroutine that includes that. Programmers now use "coroutines" in a way that I have a hard time distinguishing from "threads", Pythonic "generators", and in the worst cases "something vaguely concurrent". Any given author may have a clear idea of what they mean (and in particular, I'm not making any specific accusations about the author of this piece) but the term is rapidly approaching uselessness in the general programming community.
> I may be opinionated, but I've done concurrency in many languages and never ever have I seen anything less readable than coroutines.
For instance, I can make API requests at a higher rate than most APIs will let me from a single threaded async client.
I wish I could have slept through the circa 2012 Node.js hype cycle like this person clearly did.