

Even after ten years, Rust still hasn't settled down enough so that you could feel safe choosing it for production - unless you were prepared to put in the extra effort. Issues of ownership may get better over time, but at the moment something that isn't getting better are the breaking changes.
#Rust programming language we to mainstream how to
What it is a guarantee of is that you will spend time fighting Rust's ownership rules until you find out how to think about it correctly.

Of course, isn't the only way to write safe code and even if you do know and use Rust it isn't a guarantee that your code will be safe. People who don't know the language will sometimes refer to it as the only way to write safe code. So Rust seems to be back where it was? Not quite, we all seem to have a lot invested in Rust these days. You can see Rust's strange progress over its ten years: There are hardly mainstream, general purpose, languages. Mind you in absolute terms the accolade isn't that great - at 19 is Classic Visual Basic, 18 is Scratch, which, as we reported re-entered the top 20 in April, and 17 is PL/SQL. But if you look at the bottom of the table you see a new entry - Rust at position 20 up from 38. This is only slighly interesting as they are so close that statistical variation will cause such swaps. The top three, C, Java and Python, are still the top three, but C has pushed Java off the top spot. This month's TIOBE index is out and we weren't going to write a news item about it because at first sight its boring. Yes, yes it's all nonsense, but it's fun and has some sort of correlation with something and if you are a Rust fan, count me in, you can use it to browbeat others - Rust is in TIOBE's top twenty languages!
