It's a nice language, the first language where having learned it I really wanted to rewrite my existing code in it.
If you enjoy learning languages (you listed five) it isn't hard to play around with some Rust and see if you like it, the entry "price" in terms of time and effort is minimal, the tools even by default generate a Hello, World example so you don't have that intro-to-Java moment where there's like eight lines of inexplicable boilerplate to copy from the slides before you can print a word on the screen (what is "Public static void" and what are "String[] args" ?)
But it isn't a panacea, all the languages you list are Garbage Collected, so for you Rust would be a crash course in ownership / lifetimes. If you write enough of the languages you mentioned you might have touched on this, a database handle for example might have a distinct lifetime, the IDisposable interface in C# is in this ballpark, you may have some clue. In Rust this gets real immediately for even mundane seeming objects like a String (the mutable string type), and you may find that it's more productive to do work where you're unclear about the object lifetimes in a garbage collected language where it isn't your problem. Or you might find it all makes perfect sense and you wonder why anybody wasted their time with these GC languages. People vary.
> you may find that it's more productive to do work where you're unclear about the object lifetimes in a garbage collected language where it isn't your problem.
This is exactly why I haven't ventured into Rust yet.
But lately I've taken interest in WASM and HW programming. I write in Go-WASM, But have realized that concurrency prowess of Go is irrelevant in WASM as threads are not implemented yet, More over it's a recipe for getting the UI thread blocked.
And GC languages are generally a pain on HW with low memory.
Is Rust worth the effort for writing WASM? Thereby gaining the necessary skills to apply in HW systems programming?
If you enjoy learning languages (you listed five) it isn't hard to play around with some Rust and see if you like it, the entry "price" in terms of time and effort is minimal, the tools even by default generate a Hello, World example so you don't have that intro-to-Java moment where there's like eight lines of inexplicable boilerplate to copy from the slides before you can print a word on the screen (what is "Public static void" and what are "String[] args" ?)
But it isn't a panacea, all the languages you list are Garbage Collected, so for you Rust would be a crash course in ownership / lifetimes. If you write enough of the languages you mentioned you might have touched on this, a database handle for example might have a distinct lifetime, the IDisposable interface in C# is in this ballpark, you may have some clue. In Rust this gets real immediately for even mundane seeming objects like a String (the mutable string type), and you may find that it's more productive to do work where you're unclear about the object lifetimes in a garbage collected language where it isn't your problem. Or you might find it all makes perfect sense and you wonder why anybody wasted their time with these GC languages. People vary.