> the article complains that async/await 'infects' all the code that touches it and forces the callers to use async/await too. But isn't the same true with go c

> the article complains that async/await 'infects' all the code that touches it and forces the callers to use async/await too. But isn't the same true with go channels ? I'm not familiar with go, but I don't think so: stackful coroutines abstract better than the stackless kind.