To make things a bit weirder in the Rust land, whilst async programming is the first class citizen, the standard library (i.e. async_std) is rather limited or a

To make things a bit weirder in the Rust land, whilst async programming is the first class citizen, the standard library (i.e. async_std) is rather limited or at least seems like it to an untrained beginner’s eyes like my own. This highlights one of the troubling things about naming your project "async_std" while not having any participation from or endorsement by the people who actually work on Rust's standard library. async_std is a community project, as unofficial as any other random crate. I don't know whether its creators predicted it was prone to this kind of misunderstanding, but IMO they don't take enough measures to disambiguate this in the project docs & repo. To viewers who don't know better or dig deeper, async_std has an unearned, false sense of legitimacy by its name alone. Some newcomers like the article's author think the crate is fairly literally "std, but async". Not so. It's just a few devs doing their own thing. Inspired-by. IMO async_std (and smol) are non-starters since ~2022 and nearly dead with regards to repo activity, and anyone starting net-new async Rust work should be deciding between tokio or embassy.