Re:Choosing a Rust web framework
by steveklabnik on Tuesday July 07, 2020 @01:59PM
(#23762078)
The language does not prefer anything, one way or the other.
The community is overall very excited about async right now, and so the community may expect things to be async-first, even if the language itself does not have a preference.
Is this actually true? I've heard mixed things about this, including that Rust itself has no particular position on the preferred concurrency model. Even the async book[1] says:
> It's important to remember that traditional threaded applications can be quite effective, and that Rust's small memory footprint and predictability mean that you can get far without ever using async. The increased complexity of the asynchronous programming model isn't always worth it, and it's important to consider whether your application would be better served by using a simpler threaded model.
[1] https://rust-lang.github.io/async-book/01_getting_started/02...