Core Viewpoint - The article discusses Linus Torvalds' role in maintaining the Linux kernel, emphasizing the importance of stability and the rigorous process of code merging and bug fixing, while also addressing the potential role of AI in this context [1][3][24]. Group 1: Linux Kernel Maintenance Process - The Linux kernel has over 40 million lines of code, and Torvalds claims he is no longer a programmer but focuses on overseeing the project [1]. - The kernel is released every 9 weeks, with approximately 12,000 submissions during each merge window, which Torvalds manages by merging code for two weeks and then spending the next seven weeks identifying and fixing bugs [13][15][16]. - A strict principle of "no regressions" is maintained, meaning no new bugs or backward compatibility issues are allowed [2][22]. Group 2: AI's Role in Development - Torvalds expresses skepticism about the hype surrounding AI but acknowledges its potential as a tool for code review and maintenance, rather than for writing code [24][25]. - He believes that AI can help streamline the code review process and has seen promising results from AI tools in identifying bugs [26][27]. - The comparison is made between AI and the advent of compilers, suggesting that while AI may enhance productivity, it is ultimately just another tool in the developer's toolkit [28][29]. Group 3: Challenges in Code Maintenance - The difficulty of maintaining the "no regressions" rule is highlighted, as changes can lead to unforeseen issues that affect existing applications [30][31]. - Developers often face the temptation to introduce new features, which can conflict with the stability required for widely used systems like the Linux kernel [32][33]. - Torvalds emphasizes the need for careful management of changes to avoid breaking existing functionality, advocating for the use of new interfaces while keeping old ones operational [34].

Core Viewpoint - Linus Torvalds emphasizes the importance of maintaining stability and backward compatibility in the Linux kernel, asserting that there are no shortcuts in the development process and that AI should be viewed as a tool rather than a revolutionary change in programming [2][4][25]. Group 1: Linux Kernel Development Process - The Linux kernel codebase has surpassed 40 million lines, with a release cycle of approximately 9 weeks, during which around 12,000 submissions are processed [2][14]. - During the merge window, Torvalds typically spends two weeks merging code and the following seven weeks identifying and fixing bugs, ensuring the kernel is in optimal condition before release [16][17]. - The principle of "no regressions" is strictly enforced, meaning that new code must not introduce bugs or break backward compatibility [3][23]. Group 2: Role of AI in Development - Torvalds expresses skepticism towards the hype surrounding AI, stating that while he dislikes the term, he recognizes the potential of AI as a valuable tool in code maintenance and review processes [25][26]. - AI tools are being explored to assist in code reviews and to prevent problematic code from being submitted, which could streamline the development workflow [26][27]. - The comparison is made between AI and the advent of compilers, suggesting that while AI may enhance efficiency, it is ultimately just another tool in the developer's toolkit [28][29]. Group 3: Challenges in Kernel Development - The difficulty of maintaining the "no regressions" rule is highlighted, as changes may not be immediately apparent and can lead to issues for users who upgrade to newer kernel versions [31][32]. - Developers often face the temptation to introduce new features that may disrupt existing functionality, complicating the maintenance of stability [33][34]. - Torvalds emphasizes the need for a careful balance between innovation and maintaining a reliable codebase, advocating for the use of new interfaces for new features while keeping old ones functional [34][35].

Core Viewpoint - The introduction of Rust into the Linux kernel has transitioned from an experimental phase to being recognized as a long-term component, marking a significant shift in the kernel's development approach [2][6]. Group 1: Historical Context and Development - The Rust for Linux project began in 2020, aiming to assess whether Rust could justify the additional complexity it brings to kernel development [4]. - Initially, Rust code was limited and marked as "experimental," indicating a cautious approach to its integration into the kernel [4]. Group 2: Key Developments and Milestones - Over 20,000 lines of Rust code have been merged into the Linux upstream kernel since 2022, indicating a shift from mere proof of concept to real engineering progress [5]. - Rust-written kernel drivers are now running in real-world environments, such as in Google Pixel devices, demonstrating Rust's practical safety benefits [5]. - The ecosystem around Rust in the kernel is maturing, with foundational libraries and tools being developed, making it more accessible for developers [5]. Group 3: Official Recognition and Future Directions - The "experimental phase" of Rust support in the Linux kernel was officially declared over at the 2025 Linux Kernel Maintainers Summit, signaling a commitment to its long-term use [6]. - Despite the end of the experimental phase, significant work remains to adapt Rust for various architectures and configurations within the kernel [6]. - The transition to Rust is seen as a long-term investment, encouraging companies and hardware manufacturers to consider Rust for future driver development [8]. Group 4: Coexistence with C - The Linux kernel will continue to primarily use C, but the focus has shifted to how Rust can coexist and complement C within the kernel [9].