3 6 Ke·2025-12-26 00:46Core Viewpoint - Microsoft has denied plans to rewrite Windows 11 using AI and Rust, contrary to statements made by an internal engineer suggesting a complete overhaul of the codebase by 2030 [1][5][10]. Group 1: Microsoft’s AI and Rust Strategy - The initial claim by engineer Galen Hunt suggested that one engineer could rewrite one million lines of code in a month using AI and Rust, aiming to eliminate C/C++ from Microsoft's codebase [5][10]. - This statement sparked significant public concern, with many questioning the feasibility and safety of such an approach, citing the potential risks associated with rewriting a legacy system with millions of lines of code [6][8]. - Hunt later clarified that his comments were misinterpreted and that the project was merely a research initiative, not an official strategy for Windows 11 [3][10]. Group 2: Concerns Over Legacy Code - Critics highlighted the complexity and historical burden of Windows' code, which has evolved over decades, making a complete rewrite a daunting task fraught with potential issues [26][28]. - The existing C/C++ code is known to harbor numerous bugs, and transitioning to Rust could introduce new challenges in identifying and resolving these issues [6][8][28]. - Microsoft has acknowledged that approximately 70% of security vulnerabilities in Windows are attributed to C/C++ code, which has driven interest in Rust as a safer alternative [15][16][22]. Group 3: AI's Role in Development - Microsoft has been vocal about its commitment to integrating AI into its development processes, with CEO Satya Nadella stating that around 30% of the code is already AI-generated, and this figure is expected to rise significantly by 2030 [35][37]. - The potential for AI to act as a bridge in transitioning from C/C++ to Rust could reduce the barriers associated with learning and implementing new programming languages [31][32]. - However, the current capabilities of AI are still not sufficient to fully automate the complex task of rewriting core system components, indicating that the technology is not yet ready for such a significant shift [32][33]. Group 4: Future Implications for Microsoft - The incident has prompted Microsoft to reconsider its pace in becoming an "AI-native enterprise," balancing innovation with caution to avoid potential pitfalls [39][40]. - The company may need to adopt a more measured approach, planning carefully to ensure that technological advancements do not lead to operational failures [41].