1. Praise for the paper’s cross‑language analysis and teaching value
- “Amazing work. It's one thing to say 'async is complex'. It's another to parse that statement so carefully as to have a cross‑language theory of async execution.” — perrygeo
- “With these dimensions of design variance defined, you could also make a closeness measure in 9‑dimensional space … Also a great teaching tool …” — alilleybrinker
2. Debate over what await actually does (static vs. dynamic suspension)
- “What is 'await' if not a synonym for 'suspend'!?” — bradleybuda
- “it's a question of whether the runtime is guaranteed to suspend at an await point or if it may choose not to” — biorach
- “There are scenarios where something might need to await and might not. Why take the hit if you are able to do something synchronously?” — nxc18
3. Comparisons of async/await’s difficulty relative to threads and other concurrency models
- “Having used both threads and async/await … I don't see how async/await is supposed to make it easier to get right.” — toast0
- “When you program with threads sanely, it takes very little for async/await to actually be the substantially more complicated and difficult‑to‑understand choice …” — jerf
- “To me it’s substantially easier to understand than threads, goroutines, or structured concurrency in Kotlin.” — slopinthebag