All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Security
Security
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Why Virtual Threads Are a Better Abstraction Than Async/Await for Concurrency

By

Armin Ronacher

16h ago· 28 min readenOpinion

Summary

The author argues that async/await is a fundamentally flawed abstraction for most programming languages, advocating instead for virtual threads as a superior concurrency model. Drawing from years of experience with async/await-based systems, the author contends that these systems fail to handle back pressure well and introduce unnecessary complexity. The piece reexamines and synthesizes arguments from previous thinkers in the field, ultimately concluding that thread-based concurrency (particularly virtual threads) offers a cleaner, more intuitive approach to managing concurrent operations in modern software development.

Source

Twitter / XWhy Virtual Threads Are a Better Abstraction Than Async/Await for Concurrencylucumr.pocoo.org

Key quotes

· 3 pulled
I'm now convinced that async/await is, in fact, a bad abstraction for most languages, and we should be aiming for something better instead and that I believe to be thread.
It's been a few years since I wrote about my challenges with async/await-based systems and how they just seem to not support back pressure well.
In this post, I'm also going to rehash many arguments from very clever people that came before
Snippet from the RSS feed
Musings about async await again and why I think virtual threads

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.