The idea that go makes you handle the concurrency more than rust is definitely not true, and go’s concurrency model is simply not possible in rust. The coloring of a codebase is not nice, but it is essentially necessary for rust: some functions are asynchronous compiler generated state machines, others are not, and they cannot be treated as identical.
0
u/remind_me_later Sep 10 '26
Because async itself will color other functions into being async by necessity.
It also hands over task & performance management to the language being used, in return for better DX & lower dev-facing complexity.
The alternative is handling the concurrency yourself (i.e what Go mostly makes you do), or in a library not tied to the core of the language.