“Fast Kernel Headers” Tree -v1: Eliminate the Linux Kernel's “Dependency Hell” (lwn.net)

Article summary

The Linux kernel's "Dependency Hell" is being addressed through a patch series that refactors the header-file hierarchy, making it more maintainable and less brittle. This change adds around 100k lines of code, but reduces build time by 50%. The patch series aims to decouple high-level headers from others and automate dependency handling. The goal is to improve maintainability, rather than just build time.

Main themes

• Linux kernel development
• code maintainability
• build time optimization
• decentralization vs centralization
• email vs GitHub/GitLab
• code complexity and scalability

What commenters say

• Adding 100k lines of code to the Linux kernel is a significant change that requires a strong justification, such as improved maintainability.
• The benefits of the patch series, including reduced build time and improved maintainability, outweigh the costs of added code complexity.
• The use of email for kernel development is preferred by some due to its decentralization and accessibility, despite potential drawbacks.
• A centralized platform like GitHub or GitLab may not be suitable for kernel development due to scalability issues and vendor lock-in concerns.
• The patch series' changes are not just about reducing build time, but also about making the codebase more maintainable and less prone to errors.
• The added code is not necessarily redundant or duplicative, but rather makes implicit dependencies explicit, improving code organization.
• The Linux kernel's development process is intentionally designed to be decentralized and resistant to central control, making email a better fit than centralized platforms.