A recent job listing shared by a Microsoft engineer ignited widespread speculation that the company was preparing to replace all C and C++ code across Windows with Rust by the end of the decade. The idea thrilled advocates of memory-safe languages and alarmed others—but the reality is far less sweeping. The post reflected a personal ambition tied to a research effort, not an official Microsoft roadmap or a rewrite of Windows.
The engineer behind the post, Microsoft Distinguished Engineer Galen Hunt, initially described a bold goal that quickly drew attention on LinkedIn. As reactions poured in, Hunt clarified that the work is part of an internal research project focused on tooling, not a mandate to abandon C or C++. He emphasized that the intent was to connect with engineers interested in the problem space, not to announce a new direction for Windows or declare Rust as a final destination.
At the heart of the project is an exploration of how artificial intelligence can help translate large codebases from one programming language to another. Hunt described the team’s aspirational benchmark as enabling a single engineer to translate one million lines of code in a month. Rust is being used as a demonstration target, while C and C++ serve as source languages, but the underlying goal is language-agnostic migration at scale.
The role being recruited for will sit within Microsoft’s Future of Scalable Software Engineering team in the CoreAI organization. The work involves building infrastructure, static analysis systems, and machine learning models that support AI-assisted code translation and modernization. The broader motivation aligns with growing industry pressure to move away from memory-unsafe languages, as studies from Microsoft and Google have shown that roughly 70% of software security vulnerabilities stem from memory safety issues.