@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
-
-
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.
-
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.
End of conversation
New conversation -
-
-
That was fast! thanks. Isn't tokio used a lot by other crates?. therefore passing on that UX to them?. also curious to know if you have early users/adopters of async_std and the "stability" of Tide and if it is also getting early adopters?..
-
I'm not sure if I'm the right person to ask about Tokio's influence on the ecosystem. But yes, we have seen a steady increase of users over time for both async-std and Tide. async-std is considered stable, while tide's core is actively being designed and has seen regular changes
End of conversation
New conversation -
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.