Rust's async story is still an embarrassment for web APIs

I came to Rust expecting the memory safety and performance everyone raves about, and for a while it delivered. Then I tried writing async Rust, and all that confidence in my code evaporated.. All of a sudden, I had to fight Pin, decipher Waker, and choose among three runtimes, before I had even processed a single request. 😮😨 The language is great. The async story is not. I want to emphasize my position. Rust was the first mainstream language to achieve memory safety in this manner. However, we must acknowledge that there is a deficiency in the ecosystem that no one dares to speak of openly. A programming language can be great and yet possess a shameful shortcoming. The gap lies in async for web work. By acting as if there is no problem, the adoption among the exact CRUD-and-endpoints crowd that Rust aims to attract is slowed. Pin, Waker, and the three-runtime shuffle You can read any developer forum thread on Pin, Waker, and fragmented runtimes. The same c