The Case Against the “Blockbuster” Release
Linus Torvalds, the architect of the Linux kernel, is doubling down on his commitment to incremental development. At the Open Source Summit, he reaffirmed that the project will stick to its steady cadence—releasing every nine to ten weeks. He remains wary of feature-heavy updates, preferring stability over the volatility of “blockbuster” releases.
During the kernel merge window, Torvalds personally oversees roughly 200 merges. His process relies on human-led code review and clear communication, not automated tools. He is firm with his maintainers: avoid last-minute fixes, as even minor adjustments can trigger regressions that far outweigh the value of an immediate patch.
Purging Obsolete Code and Legacy Hardware
To keep the kernel manageable, Torvalds is aggressively pruning the codebase. The project is systematically dropping support for hardware that no longer sees real-world use, outside of niche museum or legacy collections.
The latest casualties include 30-year-old hardware like the 486 SX processor, as the kernel moves to end support for x86 machines that lack hardware floating-point units. This cleanup extends to software as well; outdated networking standards, including ISDN and ATM, are being phased out to reduce the long-term maintenance burden.
C, Rust, and the Limits of Language
Industry excitement surrounding the Rust programming language has not swayed Torvalds’ pragmatic view of his workflow. He still prefers C for his “hack-and-slash” style, arguing that Rust is not a panacea for poor programming logic.
While Rust can mitigate specific memory-safety issues, Torvalds notes it cannot fix fundamental errors. Furthermore, the security guarantees of Rust are limited to its own modules. Interactions between those modules and the core C-based kernel remain a primary area of focus for rigorous testing.
The Hidden Costs of AI Assistance
While community members are increasingly using Large Language Models to hunt for bugs, Torvalds is skeptical of their reliability. He warns that AI-generated reports often lead to “hallucinations,” forcing maintainers to waste valuable time verifying inaccuracies instead of writing code.
Torvalds uses AI tools for his own prototyping, but he draws a hard line at the kernel level. For the Linux project, the community requires human-verified patches rather than “mindless” automated band-aid fixes.
Core Development Principles
- Development Workflow: Torvalds functions as a development lead, focusing on understanding the intent behind pull requests rather than writing raw code himself.
- Hardware Support: Linux is actively cleaning its codebase by removing support for legacy hardware, such as 386 and 486-era systems, to reduce maintenance burdens.
- Security Priorities: Verification tools for C code remain a higher priority for the kernel than a total transition to new languages.
- AI Limitations: AI tools are viewed as useful for prototyping but are currently considered a net drain on resources when used to generate unverified bug reports or patches.