If your goal is to get maximum financial payoff by getting expertise in one of the above mentioned languages which one would you choose? I know languages matter less. But still I would like to see what you guys think.
That’s the wrong question/assumption to begin with and already doomed.<p>If your goal is maximum financial payoff, it won’t be done with knowing any single programming language.<p>Pick a product/industry first, then pick the mostly optimal tool. The market cap of the product/industry will determine the payoff (unless you’re inventing a completely new sector).<p>Ex: if you work at a hedge fund as a top quant/algo person, C++ will be THE language. Being close to the money, literally trading it as the day job, will reward the most financially.<p>If you think google products and joining google will be the highest payoff, then learn golang.<p>I hear there’s a lot of rust and go in crypto, if that’s your thing (def not mine).<p>If you don’t know what product you want to work on, and are only technically minded, then it doesn’t matter, just pick one and go deep - after you master one, look at the others figure out what’s similar, what you didn’t know - all the languages have the same basic principles; some make trade offs while others provide convenience features.
"First, it's really important to say that both Go and Rust are absolutely excellent programming languages. They're modern, powerful, widely-adopted, and offer excellent performance. You may have read articles and blog posts aiming to convince you that Go is better than Rust, or vice versa. But that really makes no sense; every programming language represents a set of trade-offs. Each language is optimised for different things, so your choice of language should be determined by what suits you and the problems you want to solve with it.<p>In this article, I'll try to give a brief overview of where I think Go is the ideal choice, and where I think Rust is a better alternative. I'll also try to give a flavour of the essential nature of both languages (the Tao of Go and Rust, if you like)."<p><a href="https://bitfieldconsulting.com/golang/rust-vs-go" rel="nofollow">https://bitfieldconsulting.com/golang/rust-vs-go</a>
Go is the easiest to become proficient with.<p>C++ and Go are the easiest to get started coding something.<p>Rust has been for me the most frustrating of the three to start being productive.
C# is my daily driver. But If I had the opportunity to code in one of your languages I would pick Rust. I think its the future. But to your question of maximum financial payoff, surely there are 10X more C++ jobs out there at the ioment than Rust or Go due to the age of the language. I know C++ is long in the tooth but it isnt going anywhere and you can still land some high paying jobs if you have it as a skill.
I've been scarred by C++ from my attempts to use it back in 1997, but recently I was considering Go or Rust for my next language. Partly because I have a small work project that I might want to make for my Windows developers, without needing to have a full Python environment, so I was considering them partly because of Tauri/Fyne cross-platform kits.<p>I've ended up deciding on Rust, based largely on recommendations from people I trust that Rust is the better language. I've just done some intro videos on both, and like the look of Rust.<p>One thing to consider: Make sure that there are libraries for what you want to be building.
You could pick up Go pretty quickly when you need it. On the other hand mastering a systems language like C++ isn’t really a well defined task- its used in so many different paradigms from microcontrollers to game engines, and degrades to C which degrades to assembly- and the domain will dictate the type of C++ used. At least learning Rust is a finite task in that there is a finite set of conventions and ways to do things (not counting unsafe which again opens up writing arbitrary memory) so you will have some chance of figuring out when you are “done” going deep on Rust and have gotten close to the cutting edge.
I would say languages hardly matter at all - pick lucrative fields and then just adopt whatever the standard tooling is there. You'll probably have no issue picking up all three languages if you need to.
"Simplify to succeed, complicate to profit".<p>That brings the choice down to C++ / Rust. Rust seems to have the wave, ride the wave.<p>I know people will say, this is blasphemy, may be it is, but financial incentive is important.
Those aren’t the skills that would matter if you’re maximizing financial pay off.<p>Staff Engineer skills are where your payoff are.<p>Hard truth - most programming problems can be solved with most languages with varying degrees of optimal. But the language isn’t what’s separating a major project from success or failure - it’s usually aligning a bunch of humans and pushing them in the right direction.
If you are ok with being an employee and not owning the company, learn devops and security. Max payoff<p>Devs are expensive, sure, but I'm never hiring a dev who knows a single language. That's a red flag. Personally speaking. Like people who edit files in nano.
If money is your sole motivation and stack overflow is to believed you would be better off learning Clojure.<p><a href="https://insights.stackoverflow.com/survey/2021#section-top-paying-technologies-top-paying-technologies" rel="nofollow">https://insights.stackoverflow.com/survey/2021#section-top-p...</a><p>Rust pips Go very slightly and C++ is near the bottom (I imagine because of underpaid and overworked game devs dragging the average down?).<p>I'd take the entire survey with a pinch of salt.<p>BFung's advice is decent. I would also add:<p>- What is a problem that lots of people have that you have the skills, willpower, time and creativity to solve?<p>If you want maximum financial payoff you're better off thinking about what is the maximum value you can offer to the world through problem solving and then select the appropriate language for solving that problem. And again, if maximum financial payoff is your sole goal, you're ultimately going to want to either own your own business or join the management/executive track otherwise you're probably going to hit a pay ceiling. So you might need to simultaneously study up on business skills depending on your existing background.<p>Another thing to consider:<p>If Capital by Thomas Piketty is to be believed, capital is growing quicker than wages. So would you be better served by taking time to invest your existing wage in a smarter manner than focusing on increasing your wage? I remember working in a coffee shop in 2014 whilst in debt wishing that I had the money to invest in shares in Tesla because I'd been reading about it and it seemed like a good bet. If I had maxed out all my credit cards and invested in Tesla stock I would actually be a millionaire right now because the stock has risen by over 3000% since then.<p>Obviously that would have been an insanely risky financial strategy but I think it illustrates the point nicely that maximum financial output is a pretty hard target to optimise for. Instead, optimise to add value. Most people find this a more rewarding path emotionally, spiritually and, as a happy byproduct, often financially as well. After all, a company's share price is, theoretically, a reflection of the value it offers the world at any moment in time.