What if I replace the word
Rustup is a nice thing, but in reality for a new user there is a lot of more subtle notions to acquire before becoming productive (like acknowledging that you need a stable toolchain to compile your code + a nightly one to lint / test / benchmark).
The second thing is the ecosystem fragmentation, having some users using nightly and other stable is maybe nice for hobbyists but not for world scale collaboration scenarios. From an external point of view it really looks like the python 2/3 problem.
Here again as a newcomer I feel that the rust ecosystem is fighting against my productivity.
Error handling is not even stabilized / a consensus in Rust (failure vs error_chain).
You can call it stagnation, but on the other hand it’s one of the reason that go is so successful compared to Rust: users have all access to the same set of stable and (almost) bug free features used by modern applications (HTTP, crypto, database, encoding, language parsing, templates, math… In stdlib), and develop frameworks arround this without being worried that their work will become obsolete in 12 weeks (because it will not). There are things far from perfect (error handling for example), but it works, it just works!
On the other hand, in rust the
http library which seems to be the consensus (today, but what about in 18 weeks ?) Is
0.1.14. And it doesn’t even include a client and a server.
So if I want to create an HTTP application in rust today I should be okay with the fact that either I need to reinvent the wheel and recreate an HTTP stack (actix web) incompatible with the most popular one, either I should accept that maybe the popular one is buggy and I will need to upgrade all my code in 2 months because the fix will land in a release breaking the API.