Microsoft wants to replace its entire C and C++ codebase, perhaps by 2030
Summary
Microsoft has publicly signalled an ambitious plan to eliminate C and C++ across its codebase — potentially by 2030 — by translating large C/C++ systems into Rust. Distinguished engineer Galen Hunt set out the objective on LinkedIn, and the company is hiring for roles to build the tooling and pipelines to make large-scale migration practical.
Microsoft intends to combine algorithmic analysis with AI agents to process source code at scale, aiming for conversion productivity targets summarised by Hunt’s “1 engineer, 1 month, 1 million lines of code” North Star. The effort builds on Microsoft’s prior Rust work (tools for drivers, automatic C→Rust conversion research) but will still face vast engineering, compatibility and edge-case challenges across its expansive product and internal-IT estate.
Key Points
- Galen Hunt announced a goal to remove every line of C and C++ from Microsoft, possibly by 2030.
- Microsoft plans to use a mix of AI and algorithmic tooling to translate large codebases into Rust at scale.
- Hunt cited a productivity target: “1 engineer, 1 month, 1 million lines of code.”
- The company already has code-processing infrastructure and prior Rust initiatives (drivers, C→Rust tools, research).
- Rust’s memory-safety model is the primary motivator—reducing bugs like buffer overflows and use-after-free vulnerabilities.
- The migration will be enormous in scope and is expected to surface many edge cases automation cannot fully resolve.
- Microsoft is recruiting a Principal Software Engineer for the Future of Scalable Software Engineering group; role expects office presence in Redmond and lists salary range.
Why should I read this?
Because this isn’t just another language preference — it’s a potential seismic shift in how one of the world’s largest software vendors manages security, maintenance and technical debt. If Microsoft actually executes this, it could accelerate Rust adoption across the industry and change expectations around legacy code management. Read the detail if you care about software security, large-scale migration strategies, or the future of systems engineering — and if you want a heads-up on the kinds of tools and jobs that will follow.