# Outdated Tech Linus Still Relies On The surprising legacy tech holding back a tech guru's workflow - **Source:** [Linus Tech Tips](https://brifing.si/source/9a69ed2e-1fd3-4ff2-8a24-bbee40fa616b) - **Published:** 2026-09-27 - **Original article:** - **On Brifing:** https://brifing.si/s/0417ac8a-1cef-4b50-beb1-342a96cb8dda ## Linux creator's tech paradox Linus Torvalds, creator of the Linux kernel, still relies on outdated email clients and text-based interfaces for core development work. This contrasts sharply with modern collaborative tools used by most developers. His setup includes 20-year-old email conventions and command-line tools that predate contemporary IDEs. The persistence of these tools in his workflow highlights the tension between efficiency and personal preference in tech environments. ## Email as version control Torvalds continues using email patches for Linux kernel contributions, a method largely abandoned elsewhere. This workflow requires contributors to format changes as email attachments rather than using Git directly. The process creates extra steps but maintains Torvalds' preferred review methodology. About 5-10% of kernel submissions still follow this legacy path despite available modern alternatives. ## Terminal-centric development The developer operates primarily through terminal windows and text editors rather than graphical IDEs. His setup lacks many modern debugging and visualization tools common in contemporary development environments. This approach prioritizes keyboard efficiency over visual feedback. Torvalds has publicly criticized feature-heavy IDEs that sacrifice performance for convenience. ## Minimal hardware requirements Torvalds' development machine runs on relatively modest hardware by modern standards. He avoids high-end workstations, demonstrating that core infrastructure development doesn't require cutting-edge specs. This contrasts with many developers who prioritize hardware upgrades. The setup proves that effective coding depends more on skill than equipment. ## Resistance to web tools The Linux founder avoids web-based development platforms and cloud IDEs, preferring local tools. This reflects concerns about reliability and control rather than technical limitations. Many collaborative features in modern tools remain unused in his workflow. The stance represents a philosophical position on toolchain ownership. ## Impact on contributor experience New Linux kernel developers face a steeper learning curve due to legacy tools. The email-based workflow creates friction for those accustomed to GitHub-style collaboration. However, it enforces rigorous review standards that some argue improve code quality. This tradeoff affects recruitment but maintains development discipline. ## Security through simplicity Older, text-based tools offer security advantages by reducing attack surfaces. Their simplicity means fewer vulnerabilities compared to complex modern applications. Torvalds' setup minimizes dependencies that could introduce risks. This demonstrates how legacy technology can sometimes provide superior security postures. ## Philosophy over convenience Torvalds' tool choices reflect deeper principles about software development priorities. He values control, transparency and efficiency over modern conveniences. This approach maintains the Unix philosophy of small, focused tools. While seemingly outdated, these choices continue producing one of computing's most important codebases. ## Sources covering this story - https://www.youtube.com/shorts/zH9bqwNShiM — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._