←back to thread

Python has had async for 10 years – why isn't it more popular?

(tonybaloney.github.io)
320 points willm | 1 comments | 02 Sep 25 17:24 UTC | HN request time: 0.245s | source
Show context
svieira ◴[02 Sep 25 18:00 UTC] No.45106733[source]▶
I used to keep plugging Unyielding [1] vs. What Color Is Your Function [2] as the right matrix to view these issues within. But then Notes on structured concurrency [3] was written and I just point to that these days.

But, to sum it all up for those who want to talk here, there are several ways to look at concurrency but only one that matters. Is my program correct? How long will it take to make my program correct? Structured concurrency makes that clear(er) in the syntax of the language. Unstructured concurrency requires that you hold all the code in your head.

[1]: https://glyph.twistedmatrix.com/2014/02/unyielding.html

[2]: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...

[3]: https://vorpus.org/blog/notes-on-structured-concurrency-or-g...

replies(3): >>45109891 #>>45112550 #>>45113108 #
1. stephenlf ◴[03 Sep 25 05:41 UTC] No.45112550[source]▶
Man, that Trio [3] read was great. When we demand that all concurrent tasks must join, then we can better reason about our programs.

I already kinda had this idea while working with Rust. In Rust, Futures won’t execute unless `await`ed. In practice, that meant that all my futures were joined. It was just the only way I could wrap my head around doing anything useful with async.