async / await as they exist in JavaScript, Python, and Rust aren’t the only way to execute tasks concurrently.

That’s what I’m asking - did the comment mean that the async/await pattern is bad, or that asynchronous programming in general is bad?

asynchronous programming is the bee's knees, and my preferred mode

Asyc/await pretends to be synchronous and gets all tied in horrible knots when the sunk costs mount

Writing IO without blocking has always been second nature to me

But they are a darn convenient mental model if you’re just trying to do some basic async. The alternatives are harder to wrap your head around. Unless I’m missing some other cool pattern.

> Unless I’m missing some other cool pattern.

Explicit state machines