Rust

This whole circumstance just reminds me of COBOL. Nowadays you have scant few programmers for it, but the ones who do demand a big salary because it's such old specialized technology and often they have decades of experience in it. There's simply less COBOL programmers than there were in the languages heyday, and the ones trying to enter that market nowadays have a huge learning curve ahead of them.

The only reason most of these places that do that though, is because they wrote in COBOL to begin with decades ago, and didn't want to switch away to something more modern as other languages gained functionality and popularity.

I doubt C is ever going to go the way that COBOL has, it's too ubiquitous, but it does make one consider the language you write in and how compatible it may be not just with what exists today but what's going to exist years from the creation of that code.

The US government spending tens of millions of dollars funneling every student into STEM for the last 20 years was absolutely a coordinated attempt to drive down the cost of that labor.

This really implies a level of competence and understanding among the highest levels of management that I think we all know just isn't there.

I seriously doubt changing language would impact a senior that much...

Bruh. Just put Rust on your resume. It's not like they'll actually check and you can still Google everything.

What the hell is going on with the kerning in that screenshot? My eyes, they bleed.

Rust is a conspiracy to bring down wages! Rust is a conspiracy to replace GPL with MIT to gain control of Linux! Rust is a conspiracy to impregnate your dog!

Anti-Rust crusaders: "C is easy actually and Rust is pointlessly annoying and hard to learn"

Also anti-Rust crusaders:

If moving to another language erases 15 years of experience, you probably don't have a good grasp on the fundamentals...

Here's a shocking (/s) observation: it's about different things for different people.

For seniors like the author, it may be about companies trying to replace them with cheaper professionals. For companies, it may be about renewing the workforce. For product owners / tech leads, it could be about the opportunity of using a rewrite to pick a stack that better aligns with the problems they're trying to solve. For regulators it may be about its safety features and eliminating entire categories of common issues. For juniors, it may be about choosing a language they actually like working with.

@onlinepersona the master plan to remove old senior devs is ... to train new senior devs.

@onlinepersona ah, the time-honored tradition of The Big Rewrite 'cause it's cheap. Where do people get these horseshit ideas?