Indeed! Google just announced that Chromium will start allowing Rust contributions, and Postgresql has found incredible gains by encouraging Rust-based extensions. Rust solves real problems that C/C++ developers have experienced and felt for a long time. It's a great time to be or to become a proficient Rust developer!
I'll be 70 in a few weeks. In my professional career, I was a C/C++/C# developer. I needed to develop a backend API for an iOS app last year and decided to use Rust because of all I'd read about it. Yes, the learning curve is steep. I hung in there like grim death until the tricky bits became clear. I love the language and the ecosystem. I am still very fond of C/C++/C#, however.
Thanks for sharing your experience Glenn! You sound like a guy who absolutely loves programming computers. What are some of the favorite things you came across while learning Rust?
I have found similar things about Rust that I love as you did and you described them very well. Rust, at first, seems rather straightforward, then downright intimidating and hard, then approachable again.
And I couldn't have said it any better where you point out the sense of trust one can have in the rigor of Rust resulting in a rigor in one's own code. This is not to be understated - it's a very significant part of any language. This trust is something I only partially experienced with C/C++...until it would frustratingly violate my trust at runtime by frequent undefined behavior scenarios and providing little guidance from the languages themselves!
When I betted on Rust other laughed at me. Today it pays off.
Indeed! Google just announced that Chromium will start allowing Rust contributions, and Postgresql has found incredible gains by encouraging Rust-based extensions. Rust solves real problems that C/C++ developers have experienced and felt for a long time. It's a great time to be or to become a proficient Rust developer!
I'll be 70 in a few weeks. In my professional career, I was a C/C++/C# developer. I needed to develop a backend API for an iOS app last year and decided to use Rust because of all I'd read about it. Yes, the learning curve is steep. I hung in there like grim death until the tricky bits became clear. I love the language and the ecosystem. I am still very fond of C/C++/C#, however.
Thanks for sharing your experience Glenn! You sound like a guy who absolutely loves programming computers. What are some of the favorite things you came across while learning Rust?
And a big thanks for reading!
The first thing was rigidity. I knew the crates I employed were as rigorous as the code I was using to implement their features. That's real trust.
I liked the syntax and the struct/enum/trait/impl model. It's crisp and clean, unlike some of the vague C/C++ code I've encountered.
Error handling is a key feature as well. (Ok || Error) handling is much more robust than (try || throw).
The code is easy to understand once you understand its eccentricities. Reading crate code is not as difficult.
I have found similar things about Rust that I love as you did and you described them very well. Rust, at first, seems rather straightforward, then downright intimidating and hard, then approachable again.
And I couldn't have said it any better where you point out the sense of trust one can have in the rigor of Rust resulting in a rigor in one's own code. This is not to be understated - it's a very significant part of any language. This trust is something I only partially experienced with C/C++...until it would frustratingly violate my trust at runtime by frequent undefined behavior scenarios and providing little guidance from the languages themselves!