✳flâneur — a map of the web's best reading

Async Rust Is A Bad Language

bitbashing.io · 2,099 words · saved by 1 readers

But to get at whatever the hell I mean by that, we need to talk about why async Rust exists in the first place. Let’s talk about: Suppose we want our code to go fast. We have two big problems to solve: We want to use the whole computer. Code runs on CPUs, and in 2023, even my phone has eight of the damn things. If I want to use more than 12% of the machine, I need several cores. We want to keep working while we wait for slow things to complete instead of just twiddling our thumbs. Sending a message over the Internet, or even opening a file1 takes eternities in computer time—we could literally do millions of other things meanwhile. And so, we turn to our friends parallelism and concurrency. It’s a favorite hobby of CS nerds to quibble over distinctions between the two, so to oversimplify: Parallelism is about running code in parallel on several CPUs. Concurrency is about breaking a problem into separate, independent parts. These are not the same thing—single-core machines have been runn

But to get at whatever the hell I mean by that, we need to talk about why async Rust exists in the first place. Let’s talk about: Modern Concurrency: They’re Green, They’re Mean, & They Ate My Machine Suppose we want our code to go fast. We have two big problems to solve: We want to use the whole computer. Code runs on CPUs, and in 2023, even my phone has eight of the damn things. If I want to use more than 12% of the machine, I need several cores. We want to keep working while we wait for slow things to complete instead of just twiddling our thumbs. Sending a message over the Internet, or eve

Explore this link on the map →

saved by

related reading