Oddbean

▲ ▼

 @bf1b0fad @04022626 Rust is still beta:
Calling the whole language "beta" because one feature is missing is kind of ignorant?
There is a temporary solution for async traits in the ecosystem (the crate async_trait). The better, long term solution is being worked on! It is in the stabilization phase.

▲ ▼

 @bf1b0fad @04022626 The standard library is anemic:
Maybe just check out the situation with cryptographic functionality like random number generators in the standard libraries of other languages. The standard library should only contain what will not change (because of backwards compatibility).
Often, cryptographic methods can't be proven to be safe, they are only safe until someone proves otherwise or computer power gets exponentially higher. This makes them change every couple of years.

▲ ▼

 @bf1b0fad @04022626 Async is hard:
We had such a discussion in the last days after the (technically inaccurate) post "Async Rust is a bad programming language". See community responses :)

Reducing Rust to IoT, Security and Webassembly is also very ignorant. Rust is a general purpose language that you can use as low level as you want.

Here is a technically better article, but this time against Go:
https://fasterthanli.me/articles/lies-we-tell-ourselves-to-keep-using-golang

▲ ▼

 @5150cec1 @bf1b0fad @04022626 

is there a concise summary somewhere of what was wrong with the async rust article?

▲ ▼

 @1c66f3fe I found this an interesting article with Reddit discussion: https://www.reddit.com/r/rust/comments/16ebdi1/why_you_might_actually_want_async_in_your_project/

But it is biased towards smol. Personally, I would recommend to stick to Tokio especially if one is just starting with async.