←back to thread

Flattening Rust’s learning curve

(corrode.dev)
451 points birdculture | 1 comments | 13 May 25 22:25 UTC | HN request time: 0.001s | source
Show context
Havoc ◴[13 May 25 23:42 UTC] No.43979116[source]▶
I thought it was quite manageable at beginner level…though I haven’t dived into async which I gather is a whole different level of pain
replies(1): >>43979133 #
echelon ◴[13 May 25 23:45 UTC] No.43979133[source]▶
Async and the "function color" "problem" fall away if your entire app is in an async runtime.

Almost 90% of the Rust I write these days is async. I avoid non-async / blocking libraries where possible.

I think this whole issue is overblown.

replies(6): >>43979257 #>>43979273 #>>43979433 #>>43979524 #>>43981881 #>>43986031 #
1. sodality2 ◴[14 May 25 00:05 UTC] No.43979273[source]▶
That’s not a solution to the coloring problem any more than making everything red was in 2015 (ie, all the tradeoffs mentioned in the article [0] still apply).

[0]: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...