[jen20]

Absolutely not my experience. My experience is there is an initial large learning curve (2-3 weeks) and then you can be vastly more productive than any dynamic language, with better safety, a better library ecosystem, and better tooling.

[mijamo]

Both are overly broad generalization. If you are working on a backend for a web app I would certainly not recommend Rust and it would be a big loss of productivity compared to Python or JavaScript, or even Go.

For a game it could fit in some part but you would be very limited by the ecosystem so I would also not recommend except if you really know what you are doing and have significant resources.

For low level system programing it is pretty nice, and maybe the best alternative right now.

For a compiler I would say it depends if performance is the main priority, in that case yes, otherwise no.

There are plenty of other cases of course and for each the answer would be different.

It is not really a general purpose language that you could use without worry for everything like Python, at least not yet.

[lokeg]

Using libraries is so much easier in rust compared to many other libraries due to rustdoc. I can trust the type signatures to show me the actual usage, I can trust the code snippets to not be outdated, and above all this is consistent for all code in the entire ecosystem.

Almost always when I use python libraries I have to get used to a new documentation format, learn how to navigate it and so on. And then it has to be detailed enough to make up for the lack of type signatures. I cannot tell you how often I have to skim a significant portion of my dependencies' source just to use them. (Though there are counterexamples, stdlib and numpy in particular actually have okay docs)

[jen20]

I would absolutely do web backends in Rust, with Go as the backup choice. Python doesn’t feature in my top 10, and nor does JavaScript without TypeScript to make it even moderately reasonable.

[Andys]

Wouldn't you say this about Go before Rust?