@yoshuawuyts
I just saw this on Medium..I hope you take a look at it and give your opinion/take on it..
“Rust Async and the Terrible, Horrible, No Good, Very Bad Day” by Kevin Hoffmanhttps://link.medium.com/CGCO515P04
-
-
Replying to @hernino25
These all sound like fair critiques of the current state of async in Rust. More specifically they seem to touch on some of the design choices of Tokio and Rusotto. My general take on async Rust is that it's still early days. It's technically sound, but the UX is still wip.
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts @hernino25
Much of my work has been focused on finding ways to improve the UX of async rust. Covering frameworks, common patterns, and foundational libs The diagnostics and async foundations WGs are hard at work to improve the compiler side of things as well: better errors matter a lot.
1 reply 0 retweets 1 like
In the end I'd like to see a continued trend to migrate shared code into the standard lib. Having a block_on function, async fn main, Stream, async Read/Write etc. are all core. But async is currently only in it's MVP stage, so things aren't quite as smooth yet as they could be.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.