200
Rust is now a government conspiracy (programming.dev)
submitted 2 years ago by to c/rust@programming.dev
73 comments fedilink hide all child comments
 

It's getting more and more unhinged on LinkedIn.

A linkedin post by a Senior Embedded Engineer stating: Using Rust is a political solution to deskill a generation of coders to replace higher-cost labor with lower The push for Rust isn't just a technical decision - it's a calculated economic strategy. By forcing rewrites of stable systems in a new language, companies effectively reset the clock on developer experience and expertise. When a C/C++ codebase with 30 years of institutional knowledge gets rewritten in Rust, senior developers with decades of experience suddenly compete on more equal footing with juniors who just graduated. Your 15 years of C++ optimization knowledge? Now worth less than a 22-year-old's six months of Rust bootcamp training. This isn't about memory safety - it's about labor costs. Companies call it "modernization" while quietly erasing the premium they'd otherwise pay for experience. The technical arguments serve as perfect cover for what's really happening: deliberately manufacturing a scenario where they can replace $250K senior engineers with $80K juniors. The pattern is familiar to anyone who's watched other industries. Create artificial obsolescence of existing skills, then exploit the resulting chaos to reset salary expectations and eliminate the leverage that comes with specialized knowledge. This is why language transitions always seem to coincide with hiring freezes and "restructuring." It's never been about technical superiority - it's about breaking labor's bargaining power.
you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 2 years ago*

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.

  • permalink
  • fedilink
  • source
    •