An Anonymous Coward writes:
After many years of waiting, version 1.0 of the Rust programming language has finally been released. The Rust home page describes Rust as "a systems programming language that runs blazingly fast, prevents nearly all segfaults, and guarantees thread safety."
Thanks to the hard work of noted Rust core team members Yehuda Katz and Steve Klabnik, Rust is now poised to become a serious competitor to established systems programming languages like C and C++.
The announcement has brought much jubilation to the followers of Rust, who have been eagerly awaiting this milestone release for so long. With only 1,940 open issues and over 11,500 issues already closed, Rust is finally ready for users to build fantastically reliable software systems using it.
That's the wrong way to think about learning.
Instead, ask yourself, what can this language (or tool, or API) do for me, or for someone else (a software business or project)? A fair amount of what distinguishes it from other languages will be preferences of the language's creator, but if the language has any attraction at all, chances are that it has some "special sauce" that elevates it above the crowd in at least some way. You should be moderately enthusiastic about learning that special sauce, because it will come up again and again in various contexts. For example, a lot of the innovations from Smalltalk were later taken up by the Design Patterns community and Gang of Four, and then were adopted wholesale (not always in an elegant way) for the likes of Java and Microsoft DCOM and .NET.
I'm cool with someone else writing JS, I can see there are many advantages to doing so.
My concern is, what code could I write, that few if any other engineers could write?
I'm into tweaky assembly code.