Posted by willm 9/2/2025
- Async is a legitimately hard to get if you are just starting to learn it, which is probably why its isn't more popular in the python community.
- If you need async, that implies you need hi I/O performance. At that point, you probably should have picked a more performant language + runtime (Java, Node), bc use case should dictate tooling.
- It's not enough to make a language + web framework to be async -- the DB drivers need to be async too (author mentions sqlalechemy got async support in 2023 and django orm is a WIP).
I like python, but not bc its async or multi-threaded. I like it bc when I use it, I know I do not have to worry about those things and the new set of problems I have to handle when I do.
For the i/o and multi-threaded perf, give me java and node (maybe erlang/elixir if I am feeling extra spicy). For the fast and easy scripting, with massive community of open source of talent and high quality libraries (including the vast majority of web app slop), give me python.
Its either because its the only language they know or they just don't really care about performance and want to finish the project fast.
And there is nothing wrong with that. In fact, this should be the norm.
like guaranteeing a close() inside a finally
asyncio is a terrible, terrible library
I use async all the time.
The evidence this post provides is that flask and Django aren’t all in on async.
That’s meaningless.