Disaster Microsoft wants to replace its entire C and C++ codebase, perhaps by 2030 - Moving to Rust with the help of AI, trannies, and Indians

  • 🏰 The Fediverse is up. If you know, you know.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account

Microsoft wants to translate its codebase to Rust, and is hiring people to make it happen.

“My goal is to eliminate every line of C and C++ from Microsoft by 2030,” Microsoft distinguished engineer Galen Hunt wrote in a recent LinkedIn post.

“Our strategy is to combine AI and Algorithms to rewrite Microsoft’s largest codebases,” he added. “Our North Star is ‘1 engineer, 1 month, 1 million lines of code.’”

Hunt’s post mentions a job ad for a Principal Software Engineer who will be expected to work on the tools Microsoft is building to pull this off.


“The purpose of this … role is to help us evolve and augment our infrastructure to enable translating Microsoft’s largest C and C++ systems to Rust,” Hunt wrote.

Microsoft has already built some tools to make the move.

“We’ve built a powerful code processing infrastructure,” Hunt wrote. “Our algorithmic infrastructure creates a scalable graph over source code at scale. Our AI processing infrastructure then enables us to apply AI agents, guided by algorithms, to make code modifications at scale.”

Whoever gets the job will work within Microsoft’s Future of Scalable Software Engineering group, a team Hunt says has a mission to “build capabilities to allow Microsoft and our customers to eliminate technical debt at scale.”

“We pioneer new tools and techniques with internal customers and partners, and then work with other product groups to deploy those capabilities at scale across Microsoft and across the industry,” he wrote.

Unlike C and C++, Rust is a memory-safe language, meaning it uses automated memory management to avoid out-of-bounds reads and writes, and use-after-free errors, as both offer attackers a chance to control devices. In recent years, governments have called for universal adoption of memory-safe languages – and especially Rust – to improve software security.

Microsoft has also called for greater use of Rust. In 2022, the CTO of the company’s Azure cloud called Rust to become the default language for new projects. Microsoft scientists have worked on a tool that automatically converts some C code to Rust.

The software behemoth has also created tools to help developers write Windows drivers using Rust.

Microsoft offers a vast array of products. The site MSportals.io lists over 500 active online portals for managing Microsoft products! The company also has a huge internal IT estate.

The effort required to re-write all that must surely be beyond enormous. It will doubtless surface huge numbers of edge cases that automation can’t address.

If you’re brave enough to want to make a contribution, the job Hunt mentions requires you to work three days a week in Microsoft’s Redmond office and pays between $139,900 and $274,800 a year. ®


The linkedin post being referred to here:

Microsoft wants to translate its codebase to Rust, and is hiring people to make it happen.

“My goal is to eliminate every line of C and C++ from Microsoft by 2030,” Microsoft distinguished engineer Galen Hunt wrote in a recent LinkedIn post.

“Our strategy is to combine AI and Algorithms to rewrite Microsoft’s largest codebases,” he added. “Our North Star is ‘1 engineer, 1 month, 1 million lines of code.’”

Hunt’s post mentions a job ad for a Principal Software Engineer who will be expected to work on the tools Microsoft is building to pull this off.


“The purpose of this … role is to help us evolve and augment our infrastructure to enable translating Microsoft’s largest C and C++ systems to Rust,” Hunt wrote.

Microsoft has already built some tools to make the move.

“We’ve built a powerful code processing infrastructure,” Hunt wrote. “Our algorithmic infrastructure creates a scalable graph over source code at scale. Our AI processing infrastructure then enables us to apply AI agents, guided by algorithms, to make code modifications at scale.”

Whoever gets the job will work within Microsoft’s Future of Scalable Software Engineering group, a team Hunt says has a mission to “build capabilities to allow Microsoft and our customers to eliminate technical debt at scale.”

“We pioneer new tools and techniques with internal customers and partners, and then work with other product groups to deploy those capabilities at scale across Microsoft and across the industry,” he wrote.

Unlike C and C++, Rust is a memory-safe language, meaning it uses automated memory management to avoid out-of-bounds reads and writes, and use-after-free errors, as both offer attackers a chance to control devices. In recent years, governments have called for universal adoption of memory-safe languages – and especially Rust – to improve software security.

Microsoft has also called for greater use of Rust. In 2022, the CTO of the company’s Azure cloud called Rust to become the default language for new projects. Microsoft scientists have worked on a tool that automatically converts some C code to Rust.

The software behemoth has also created tools to help developers write Windows drivers using Rust.

Microsoft offers a vast array of products. The site MSportals.io lists over 500 active online portals for managing Microsoft products! The company also has a huge internal IT estate.

The effort required to re-write all that must surely be beyond enormous. It will doubtless surface huge numbers of edge cases that automation can’t address.

If you’re brave enough to want to make a contribution, the job Hunt mentions requires you to work three days a week in Microsoft’s Redmond office and pays between $139,900 and $274,800 a year. ®

The linkedin post being referred to here:


Update:
It appears my post generated far more attention than I intended... with a lot of speculative reading between the lines.

Just to clarify... Windows is *NOT* being rewritten in Rust with AI.

My team’s project is a research project. We are building tech to make migration from language to language possible. The intent of my post was to find like-minded engineers to join us on the next stage of this multi-year endeavor—not to set a new strategy for Windows 11+ or to imply that Rust is an endpoint.

Original Post:
I have an open position in my team for a IC5 Principal Software Engineer. The position is in-person in Redmond.

My goal is to eliminate every line of C and C++ from Microsoft by 2030. Our strategy is to combine AI *and* Algorithms to rewrite Microsoft’s largest codebases. Our North Star is “1 engineer, 1 month, 1 million lines of code”. To accomplish this previously unimaginable task, we’ve built a powerful code processing infrastructure. Our algorithmic infrastructure creates a scalable graph over source code at scale. Our AI processing infrastructure then enables us to apply AI agents, guided by algorithms, to make code modifications at scale. The core of this infrastructure is already operating at scale on problems such as code understanding.

The purpose of this Principal Software Engineer role is to help us evolve and augment our infrastructure to enable translating Microsoft’s largest C and C++ systems to Rust. A critical requirement for this role is experience building production quality systems-level code in Rust—preferably at least 3 years of experience writing systems-level code in Rust. Compiler, database, or OS implementation experience is highly desired. While compiler implementation experience is not required to apply, the willingness to acquire that experience in our team is required.

Our team is driven by a growth mindset. We are diverse team with a wide range of skills and perspectives. We take on bold risks. We work and play well with others. We love to bring value to internal and external customers. We have learned that our diversity and growth mindset is critical to success in the rapidly changing word of AI-based tools.

Our team is part of the Future of Scalable Software Engineering group in the EngHorizons organization in Microsoft CoreAI. Our mission is to build capabilities to allow Microsoft and our customers to eliminate technical debt at scale. We pioneer new tools and techniques with internal customers and partners, and then work with other product groups to deploy those capabilities at scale across Microsoft and across the industry.

To apply, or recommend someone, visit the Microsoft Career Hub: https://lnkd.in/gvzvAiJE (Job ID 200013722).
 
Last edited:
Talk about making the best advertisement for switching to Linux.
If only, the tranny brigade is forcing coreutils to be replaced with actively broken rust migrations there too.

At this point, I see rust as a complete negative not because of any specific flaws with the language itself, but because its gone to be some weird fucking religious/political statement that attracts the absolute worst coders to its ranks, who then use its basic principles (its not memory safe, its just capable of being memory safe) as a shield against all criticism when their code fucks up - it can't be them, Rust is a perfect language that only allows perfect code, so your use case must be flawed.
 
I'll admit it's been eleventy thousand years since I did any serious coding, but this stood out to me. Since when has the goal been to create the most lines of code possible? Does no-one care any more about elegance or efficiency?
100%.

Using modern AI tools any retard can push out a million lines of code in a month. Would this be useful or good in any way? Not likely. You'd likely spend another two months fighting with compiling problems and, as stated earlier, the endless amounts of edge cases that exist. In addition to 40 years of tribal knowledge on various aspects of Microsoft infrastructure that are too expensive to really be changed.
 
' it always seems to involve keeping people farther and farther away from the hardware.

I've never used Rust so I don't know whether the garbage collection can be disabled or not and it might not seem important to most people but the idea that lower level languages like C should just be eliminated entirely because they're 'unsafe' just sounds like another way of limiting people from having complete control over their computer hardware.
I dont think Rust is as bad as parties give it credit to be. Cpp has a bunch of problems with side effects (calling some function to transform x to y and somehow variable z is changed while this is happening), unclear call scopes or footguns (its possible the + operator could be a really complex function call not obvious to the programmer that a scope change will happen to do evoking this) and undefined behavior (too hard to explain but caused by backwards compatibility + the advancement of cpu design)...

Rust attempts to address some of the problems presented here, and some it does well, but the issue youre calling out about memory safe operations is really a fundimental change of how memory is allowed to be managed... effectively this safe memory model (the ownership model) forces all references to some spot in memory (a pointer) to be a unique smart pointer, meaning only one scope can ever have access to write to that spot at any given time, and the ability to write to it is carefully passed between scopes through borrows and lifetime notations...

the real problem with this is that it forces a very specific programming pattern, rust will simply refuse to compile if you dont follow these patterns; and these patterns cannot meet every requirement, for instance, memory arenas are not really possible under the ownership model, and so rust allows you to write explicitly marked unsafe code...

So in the end, the code is still unsafe, but only on specific critical paths, while less demanding code provides an interface to this that can guarantee memory safety in that api layer...

Theres no higher level gay shit like garbage collection, its simply another notation for memory management via pointers, only now described in mutability, borrows, and lifetimes to ensure the borrowed memory does not outlive its owner.
how are you gonna talk big about "rust is the future" when you do shit like build the win11 start menu in fucking react native?
The actual TRVTH NVKE.
 
Memory safety won't save you from enjeetification. If anything it will just make the currycode even worse. Programming horrors beyond your comprehension will continue to increase in number until you flush the fucking toilet and hire straight white men again.
 
Windows 11 is so bad even normies are not moving and word on the street is a lot of enterprises are moving to mac. They are so down bad that from 10 to 11 they cannot even keep basic features like moving the taskbar https://www.windowslatest.com/2025/12/19/why-you-cant-move-windows-11-taskbar-like-windows-10/. And this is the company that's going to re-write windows? lol, lmao

The update to this is also just... obviously cope and lies?

“My goal is to eliminate every line of C and C++ from Microsoft by 2030,”
(if you remove all the C and C++ you need to rewrite the critical functions -ie. most of the kernel- in something else unless you're just not making windows anymore)
Our strategy is to combine AI *and* Algorithms to rewrite Microsoft’s largest codebases.
to enable translating Microsoft’s largest C and C++ systems to Rust
These are all directly from the linked in post.

Just to clarify... Windows is *NOT* being rewritten in Rust with AI.
And this is the update the very same linked in post.

I'm almost at a loss to express it. Like if there were two sentences "the sky is blue" immediately followed by "I did not say the sky is blue". There's nothing to explain why that's contradictory it just... is.
 
Last edited:
My comp sci program was mostly C++ with occasional forays into C. Do Indians learn Rust mostly? I'm wondering if this is yet another bid to replace American software devs with Indians.
 
My comp sci program was mostly C++ with occasional forays into C. Do Indians learn Rust mostly? I'm wondering if this is yet another bid to replace American software devs with Indians.
no. indians learn mostly java, python, and js.
rust is the favorite language of terminally online autists (including lots of trannies) who get into language wars like gamers used to get into console wars back in the day.
 
What is the deal 2030? Why does everything has to happen by then?
I've gone into graphic detail in the past about this: (((they))) calculated that the Global Economic Depression/Apocalypse, the one that should have happened in 2008 but was mitigated into a nasty as fuck Recession we never got clear of, would finally hit in 2030 as far as all of the Jewish tricks, spamming of Courage, and life spells, and clapping hands to resurrect Tinker Bell life restoration rituals will finally stop working and the duct tape holding up the economy finally rips and tears apart, causing the biggest economic Gotterdammerung society has ever seen, possibly even bigger that the 1929 Great Depression.

When economic Gotterdammerung finally hits, the old order is going to die at long last and (((they))) have full memory of what happened last time that happened: six million dead Jews, a near completely genocide of all Jews in mainland Europe, and the rise of Nazism.

As such, the (((elites))) have had a plan to save (((themselves))) via moving heaven and earth to bring back feudalism so that when Gotterdammerung finally happens, they and their power will be protected while the rabble are wiped out and replaced with third workers who will serve as (((their))) new slave caste.
 
I've been working as a software engineer for a long time now. Nearly 20 years. The majority of my career has been writing in C and Java. Along with copious amounts of Python and SQL along the way.

Rust has some cool features but I've never personally used it much. Many applications and platforms are java based so I maintain job security easily enough. That being said there is a trend among smaller applications and platforms to shift to Rust. DBT moving to their Rust "dbt fusion" application is one that comes to mind.

Microsoft following this trend is just insanity though and it will be shitshow after shitshow. Smaller apps will have success however.
 
I've been working as a software engineer for a long time now. Nearly 20 years. The majority of my career has been writing in C and Java. Along with copious amounts of Python and SQL along the way.

Rust has some cool features but I've never personally used it much. Many applications and platforms are java based so I maintain job security easily enough. That being said there is a trend among smaller applications and platforms to shift to Rust. DBT moving to their Rust "dbt fusion" application is one that comes to mind.

Microsoft following this trend is just insanity though and it will be shitshow after shitshow. Smaller apps will have success however.
Same but java, javascript sql smattering of python and php.

The reality is as you say but for some added context- ive seen attempts to move not giant code bases to Rust. It has yet to pan out well. Theres a huge reason for this...

Rewrites are often far harder and far more time consuming than a business will realize. Some programmers will say that theyre never worth it - they are wrong. Management will say its totally always doable and will reap great benefits - theyre hopelessly optimistic.

Rewrites of large code bases can be done. But one of the key things that will make it easier is good robust QA and knowledge of what the code used to do.
Microsoft pretty obviously has neither any longer. Theyre fucked frankly. They would be better off to lock in, kick out the political kingmaker castes and let the autists who really care straighten out their 11 mess

Sadly the coder who cares, is skilled and has knowledge of their system is a dying breed. We are replaced by jeets, ai, and most damningly by people who are good office politicians and jockeying for the usual broken corporate promotions and metrics. None of the "make the thing work and make it work well and document it" translates to anything anymore. The layoffs and cost cutting and forced ai usage and meet deadline line of half baked ideas line must go up behavior will continue until the system collapses.

I havent touched a windows machine in a corporate setting for years. All macbook, all Linux servers or pods/containers/vms. Legacy and highly regulated environments still use windows but MS is halfway through slaughtering their golden goose anyways
 
OK, so my work switched to Windows11 and it so damn slow. Lots of tricks had to be applied to make my laptop usable, because everything now is just so slooow.

Now, you can dislike C/C++, I personally like both, and I don't see major issue with them as long as you know what are you doing. But rewriting everything in Rust, apart from being idiotic, will definitely affect the performance.

There is no way you can get some cache performance optimization with all this paranoid attitude towards pointers and memory allocations.

idk, I am still going to use C/C++ and it's still going to be used in any area that require good performance like finance, game dev, etc. I used to think that OS is one of them....
 
Back
Top Bottom