3 ms·
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 encourag
by kibwen 8y ago
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. :)
- sidcool 8y agoInteresting. One of the reason I am learning Rust is that I don't want to do C/C++ for a long time.
- steveklabnik 8y agoThe 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.
- pjmlp 8y agoYou should still be comfortable with them, though. Specially the best practices to write good quality code. The need to interoperate with OSes, language plugins and system libraries written in C and C++ isn't going away for the foreseeable future.
- sidcool 8y agoI agree. My interest is Distributed Systems. I was confused between Go and Rust for some time, but took a leap of faith in favor of Rust.