Eh, in the last press release from Mozilla, they say otherwise: > Confidence when doing systems-level programming. For old hands, Rust’s guarantees mean you ca

Eh, in the last press release from Mozilla, they say otherwise: > Confidence when doing systems-level programming. For old hands, Rust’s guarantees mean you can spend less of your time and attention on avoiding pitfalls, which makes it possible to reach for more ambitious goals. For newer systems programmers, it means a shorter path to being able to start writing production code. > This second point is worth emphasizing. In traditional systems programming, there’s just an intense amount of discipline you need to learn in order to write production code. Because the discipline takes so long to master, and the stakes of slipping up are crashes and security vulnerabilities, most people will only trust seasoned veterans of systems programming to ship production C++ code. But with Rust, you don’t have to master this discipline to start shipping production code; you know the language has your back. As far as I can read, it states the purpose of the language is correctness, and developer productivity?