Yeah, same! I'm making my way through "The Book". Observations thus far: Other than fooling around with GatsbyJS, I've never had to work with dependencies - not sure if I'm a fan of this yet. The language is well organized. I should learn more about u8, u16, etc, data types - I haven't worked with them before and if I did, I wasn't aware that I was. `cargo check` is neat. You know that argument in C++ where one should use `std::` rather than `using namespace std`? I wonder if that argument is also applicable to Rust. Enough rambling, are you using the learning resources mentioned on the Rust Documentation or some other resources? Any you'd recommend?
Otherwise, I too hope it pays off in the future. I'm an undergraduate and at the moment, I don't know one language fully. My background in programming has been sporadic and I would argue I'm in the middle of beginner and proficient in regard to writing C/C++. I'm most likely going to end up building a C/C++/Rust skillset - hopefully it pays off, particularly for landing a new-grad gig in a few years.
Even if you don't end up using Rust in the future, having a Rust background will give you a solid foundation for writing C and C++, since Rust strongly encourages the sort of structure and idioms that are generally considered best-practices in those languages. Being inclined to structure things hierarchically when possible will also subtly help any programs you write in dynamic languages from becoming too tangled, as will the general attitude of separating data from behavior.
That said, I also encourage learning a wildly different language as well. If you know C/C++/Rust, then take a shot at something like Scheme. This is the advice that I wish that I had gotten in college, when I spent years doing nothing but Java, and then had to spend additional years practicing four other languages before I finally stopped trying to fit every program into a Java-shaped box. Having a wide variety of experiences to draw from will be useful in the long run. :)
The point above is correct in very broad strokes, but they’re still different languages. It gives you the kind of background understanding for what problems the languages are trying to tackle, and many of the idioms are related, but there’s still big differences.
Otherwise, I too hope it pays off in the future. I'm an undergraduate and at the moment, I don't know one language fully. My background in programming has been sporadic and I would argue I'm in the middle of beginner and proficient in regard to writing C/C++. I'm most likely going to end up building a C/C++/Rust skillset - hopefully it pays off, particularly for landing a new-grad gig in a few years.