Will Rust become a good career choice?

Programming languages are not the foundation of a developer career. Languages come and go. Few non-trivial applications use a single language.

Rather than mastering this or that language and try to predict the future, focus on solving business problems, adding value, implementing requirements in code, and good development practices.

If you want to learn one language that has a high chance of lasting throughout your career, learn SQL or C.

What’s good for your career is being passionate about your craft and continuing to learn. Writing rust is one example of doing that.

I do see a lot of new startups using Rust and it’s becoming more common in server side environments. It’s probably worth learning.

Say a Uber driver asked you if driving a Honda sedan was good for his driving career. What would you say to him.

Or if you prefer a more historical analogy it’s like a free mason saying is using one particular brand of construction materials good for his career. What would you say to him.

Don’t forget we software engineers are just modern day free masons.

Whether rust becomes a good choice or not is based directly on what you learned from using it and not just developing with it. A goog Career is based knowledge and or experience compounding. When you start with that in mind the language doesn’t matter as much as the learning. Language is just a tool at that point. Sure knowing how to use multiple tools is good. But that kind of differentiator will only get you so far.

Good luck!

My view is that Rust is pretty much where Go was about 3-4 years ago. About to see a lot of strong adoption and emerge as a pre-eminent language for writing backends. Strong library support and first class tooling is probably the only thing holding it back, but I'm hearing of more and more companies starting to use it. So it's definitely going to be a good bet to learn it.

Best way to learn Rust is going to be finding a way to get it into your current job. Write a small CLI tool in Rust, or spin up a small service in Rust. Make sure it's not on the critical path so that even if you're the only one who knows it, nothing horribly bad will happen. Ideally, see if you can get a coworker to learn it with you and contribute so multiple people know it. This helps engineering managers/directors get more comfortable with adopting a new language and tech. This might have to happen in your spare time initially, but hopefully if you're successful at it, you can start to use Rust at work and get the credibility you're looking for.

I went looking for a job one year ago, and I critically analyzed if I should position myself towards a future with Rust. That resulted in a note to self: a revolution it will be, and I have to add my 2ct, sooner rather than later.

Rust and the electric vehicle are totally comparable and will follow the same adoption curve at about the same time. That much has already been decided. In about 2 years time the transition will be in obvious to everyone. This is a decision driven by industry, managers and $hit, not developers.

Electric cars offer a superior ride, no maintenance, no pollution and often drive themselves. And so does Rust, uniquely. Aware industry must be, or extinction threatens. That reality is 5 years out, and is part of "software" finally coming of age.

We'll leave the diapers, and the crap that software is full of, behind. It'll not be just Rust, but Rust uniquely. Meaning that this change reinforces Rust's moral leadership.

I was in the exact same position and ended up giving up on Rust due to the opportunity cost despite having spent considerable time on reading the book and writing some toy code.

The way I see it, there's an infinite amount of things you can learn, and you have to optimize for whatever gives the most bang for your buck. That buck being time spent.

Rust is very intriguing, but that alone wasn't enough for me to keep devoting time into learning and continuously brushing up on it. Spending time on fundamentals and languages and tools which I have a daily use for gave me a better return on investment.

No idea about the commercial prospects but if you haven't used any modern statically typed languages yet (Haskell, Rust, Scala, maybe ML/OCaML, or some of the more pointy headed ones like Coq) then I think getting some understanding of these is an important part of your tool set, even if you don't use it at work. They used to say the same thing about Lisp and it's still true.

I've spent a fair amount of time on Haskell and it's been worth it even though I haven't ever directly used it at work for anything significant. Rust at worst seems the same way.

I think people have an exaggerated expectation about Rust even though it's good at what it does. But if you really want to do low level development, then learn C first along with a good OS theory book and perhaps a compiler engineering and networking book. Those are the three areas (except for embedded programming) that Rust is being used right now.

A developer is an architect of solving problems.

The language is the material / tool used to solve the problem in question.

As we learn we know when to use X tool or language to solve Y problem.

I think it’s on the way out tbh.