(Quite) A Few Words About Async
I’ve had a few conversations about async code recently (and not so recently) and seen some code that seems to make wrong assumptions about async, so I figured out it was time to have a serious chat about async, what it’s for, what it guarantees and what it doesn’t.
I’ve had a few conversations about async code recently (and not so recently) and seen some code that seems to make wrong assumptions about async, so I figured out it was time to have a serious chat about async, what it’s for, what it guarantees and what it doesn’t. Most of the code in this entry will be written with Python syntax (and often Python libraries), but with a few minor exceptions, we’ll be discussing concepts that are valid across languages. There’s more than one kind of performance We all know about performance, right? I mean, there is some task we want our code to do (display…
saved by
related reading
- How Python Asyncio Works: Recreating it from Scratchjacobpadilla.com
- Async Rust Is A Bad Languagebitbashing.io
- Notes on structured concurrency, or: Go statement considered harmful - njs blogvorpus.org
- What Async Promised and What it Delivered — Causalitycausality.blog
- TypeScript Structured Concurrencythecandidstartup.org
- A Design Space Exploration of Async/Awaitcel.cs.brown.edu
- Let futures be futureswithout.boats
- python - How does asyncio actually work? - Stack Overflowstackoverflow.com
- Introduction - Asynchronous Programming in Rustrust-lang.github.io
- Python's asyncio: A Hands-On Walkthrough – Real Pythonrealpython.com
- Why choose async/await over threads? | Hacker Newsnews.ycombinator.com
- What the heck is the event loop anyway? | Philip Roberts | JSConf EUyoutube.com