Crust of Rust: async/await

there is a chapter on async in comprehensive rust and rustbook which ought to bring you up to speed there is the async book but it is largely unfinished you can watch John Gjengset's crust of rust async, decrusting tokio, and why what, and how of pinning in rust then there are tokio-lessons and tokio tutorial which teach how to use tokio runtime and there are also good blogposts by phil-oop and rose wright on how async works [link] [link] [link] ▶ this video [link] [link] [link] [link] [link] [link]

in “Async Rust never left the MVP state” · View on HN

Impressive! Especially the part on async where they built up the Future trait and runtime from first principles. If it interests you, these two videos are also great deep dives into Rust async [1] [2]. Rust's model is a little different from other languages in a powerful way. [1] [link] [2] ▶ this video

in “Learning Async Rust with Too Many Web Servers” · View on HN

Very interesting insight from Graydon, in hindsight I too would have loved something more towards ML than C++. I never liked the kitchen sink approach that I see first C++, now Rust moving towards, but I respect what Rust has managed to solidify into. It's a good language. That said, I still hate async with a passion, it makes the language more complex and not very elegant (i.e. function coloring). And now that I know how it works behind the scene (thanks to Jon Gjengset [1]), it feels so complicated and hacky, a mediocre very high level concept that someone managed to implement as a zero-cost abstraction. Impressive, but still a bad idea. I'm sure the pro of having a BDFL instead of a committee is being able to follow a singular vision, instead of trying to appease members by adding the fad du jour which might stray a little too far from the original vision. Too many chefs in the kitchen and all. 1: ▶ this video

in “The Rust I wanted had no future” · View on HN