Michael S (already5chosen.delete@this.yahoo.com) on July 12, 2021 3:58 am wrote:
> I don't know.
> I read through Rust tutorial and decided that I don't like it, certainly would not use
> it for code that I do for my own pleasure and would never use it for production code at
> my own initiative. Still could use it if management insists, but that's unlikely.
>
> [O.T.]
> For comparison, I read through Go manual and found it palatable.

I can relate to that, Rust is fundamentally different then C/C++ while Go is not. And over time Rust has grown more and more distant from other system languages so when you switch over you need to embrace new concepts. Five years ago I would have said that Rust's learning curve was steep - and it was - now it's not anymore, unless you're coming from years of work on traditional system languages. That's to say a kid these days can pick up Rust pretty easily as his/her first system language - just like I did with C many moons ago - but expert programmers have a harder time due to the fundamentally different approach. Learning Rust is easy, learning idiomatic Rust is still hard and requires some time to un-learn old behaviors (e.g. it is very unlikely for me to write a loop in Rust code, but learning the language won't make it immediately apparent until you familiarize yourself with the standard library).

I'd recommend reading some of Amos Wegner's excellent blog posts for a through description of how Rust and C/Go differ WRT abstractions, types and API design. Some of his posts are very long as he spends a significant amount of time going over the reasoning behind every design decision, but I think they're worth your time. Here's my recommendations:

• I want off Mr. Golang's Wild Ride


• Working with strings in Rust


• Abstracting away correctness

I'd also recommend the equally long and extremely thorough Rust is for Professionals from Gregory Szorc, another former mozillian.

Though even that post misses some aspects that make Rust a joy to use. One being portability. After having learned how to deal with native paths in Rust going back to other languages is a chore.