AI Coding Assistants vs Compilers: Torvalds’ Core Argument
The debate over AI coding assistants is about whether they genuinely "write" most modern software or simply extend a long tradition of automation in programming, where tools like compilers, assemblers, and editors already transform human intent into executable code across several layers of abstraction. Linus Torvalds’ point is blunt: when startup founders brag that ninety or ninety‑nine percent of their code is written by AI, they are ignoring the far more basic reality that one hundred percent of their binaries have always been emitted by compilers. By reframing the conversation this way, Torvalds turns the hype on its head. He calls AI “a great tool, but it’s a tool,” pushing back on marketing that treats AI as the true author of a codebase rather than another step in a familiar pipeline from human-readable source to machine code.
Compilers as the Original Automation Revolution
Torvalds’ irritation at claims that ninety-nine percent of code is written by AI is rooted in a historical view of compiler automation. For decades, compilers have translated languages like C and C++ into machine instructions, yet no one has claimed that their systems are "written by GCC" or similar tools. He argues that describing AI as the author while ignoring compilers is a selective use of abstraction meant to make a marketing point. In his view, AI sits above the compiler in the stack, not outside it: human intent becomes AI-generated source, which compilers then turn into binaries, and assemblers into machine code. Torvalds has even compared productivity gains, saying AI might give a tenfold boost while compilers gave programmers something closer to a thousandfold leap, underscoring that the deepest shift in coding automation already happened when compilers freed developers from wrestling with raw opcodes.
Linux Kernel Development: Using AI Without Letting It Drive
Torvalds’ perspective on AI coding assistants is shaped by day-to-day Linux kernel development, where stability matters more than hype. At Open Source Summit India 2026, he stressed that Linux 7.1 is part of a long pattern of "steady progression of continued improvements" rather than splashy, disruptive releases. That cadence continues with a release schedule of roughly every nine to ten weeks, even as AI puts pressure on workflows by automatically finding subtle bugs that stress the community. He now works as a development lead rather than a hands-on programmer, running around 200 merges in a two‑week window during kernel merge periods and focusing on intent behind pull requests more than direct coding. Other maintainers have started using AI tools for patch checking, but Torvalds remains unusual: he mainly uses Git, email, and search, saying he prefers to "work with people, not tools" when making decisions about what enters the kernel.
AI Assistance Is Not Authorship in Open Source
The distinction between AI assistance and code authorship becomes concrete in open-source projects like the Linux kernel. Torvalds insists AI is a tool, and that the programmer who understands intent and correctness stays irreplaceable. For personal experiments, he uses large language models as prototypers, acknowledging that "quite often the code is not usable in that form" but can help try out ideas. Yet he is clear that LLMs are not at the level needed for kernel fixes. He has even admitted his earlier "10x" productivity estimate for LLMs was "not scientific… that was pulled out of my ass number," and that until early this year, the community saw more junk than useful code from such tools. This attitude reinforces a simple principle: AI can sketch solutions, but humans still own the responsibility for the final patch, its design, and its long‑term impact on the system.
Why Kernel Maintainers Stay Skeptical of AI-Generated Patches
Despite industry enthusiasm and predictions that ninety to ninety‑five percent of code will soon be AI-generated, kernel maintainers are wary of open-ended AI contributions. Torvalds describes many AI-generated patches as "mindless band-aid" fixes that solve a specific symptom while leaving the underlying bug waiting to appear elsewhere. The Linux community has had to push back: if someone finds a bug using an LLM, they are expected to propose a patch and act as a human partner in a back-and-forth, rather than throwing a machine-written report over the fence. Worse, bug reports that look valid can turn out to be hallucinations, consuming significant human time before being exposed as false. Meanwhile, AI tools also find real "interesting bugs," increasing load on maintainers even as the project removes obsolete hardware support, like x86 machines without hardware floating point that will be dropped in Linux 7.2. The net effect is cautious adoption: AI is welcome as a helper, not as an unsupervised author.
