Linux Creator Linus Torvalds Expresses Enthusiasm for AI in Software Development

Linux creator Linus Torvalds has expressed his enthusiasm for using artificial intelligence in software development, a sentiment that sets him apart from many open-source developers who remain skeptical about AI's role.

Torvalds made these remarks during an interview at the Open Source Summit Europe, where he discussed his views on AI with his friend and colleague Dirk Hohndel. Despite the reservations held by some in the community, Torvalds sees AI as a valuable tool that can enhance the development process.

However, it's essential to note that Torvalds' endorsement of AI is not without caveats. He emphasized the need for responsible use, particularly when working on critical projects like the Linux kernel. In such cases, AI-generated patches and bug reports must be carefully evaluated to prevent overwhelming maintainers.

Torvalds reflected on his changing perspective towards AI programming, which has evolved over time. Initially, he believed that AI was not effective in generating quality code, but now he appreciates its potential as a complementary tool.

According to Torvalds, using AI correctly is crucial in making the most of its capabilities. He likened AI to a tool that can simplify and streamline programming tasks, allowing developers to focus on more complex and creative aspects of software development.

As a maintainer rather than an active kernel programmer, Torvalds' role involves collecting and reviewing contributions from other developers. Despite not being directly involved in the core development process, he still finds programming enjoyable and believes that AI can be a valuable asset when used responsibly.

The software engineering landscape has undergone significant changes over time, making it increasingly challenging for developers to see the value in their own contributions.

As a result of this high bar, many programmers feel their efforts are overshadowed by polished and professional programs that have been refined through rigorous testing and iteration.

However, Torvalds suggests that "vibe coding" can be a refreshing alternative, allowing developers to find joy and relevance in programming even if they're not working on complex projects.

This approach enables new programmers to tackle tasks they might otherwise struggle with, giving them a sense of accomplishment and confidence in their abilities.

Torvalds' own experience with AI reflects this idea, he used it as a tool to improve his guitar pedal project's user interface, which was initially clunky and outdated-looking.

The integration of artificial intelligence (AI) in code reviews has been a topic of discussion among Linux kernel maintainers. Torvalds mentioned that Sashiko, an agentic Linux kernel code review system, now publishes its public reviews on the Linux Kernel Mailing List (LKML). This move indicates a shift towards increased transparency and collaboration.

Some subsystem maintainers have started requiring AI-reviewed patches before accepting them, while others are expected to follow suit. The use of AI in this context is not meant to replace human judgment but rather augment it by identifying potential issues that may have gone unnoticed.

AI tools can detect genuine security vulnerabilities and surface problems in outdated drivers that have been overlooked for years. Torvalds acknowledges the value of these fixes, despite recognizing their associated costs. However, he also notes that AI-driven code checking has become a source of stress for maintainers.

The challenge lies not in generating patches but in getting useful work through review without overburdening those responsible. This is evident from the recent Linux Kernel Maintainer Summit discussion, where three-quarters of the conversation centered on making AI generation and review less stressful and more beneficial.

To address this issue, maintainers are exploring ways to make AI-generated code reviews more efficient and effective. The goal is to strike a balance between leveraging technology and minimizing its impact on human resources.

While some may view AI-driven code checking as a threat, Torvalds sees it as a means to improve the Linux kernel's overall quality and security. He recognizes that AI has limitations but believes it can be a valuable tool when used judiciously.

The development process of Linux has undergone significant changes since its inception 35 years ago. In the early days, Linus Torvalds relied on manual tracking of changes through tarball patches and regularly distributed updated source code.

Torvalds would make internal patches every day and release them at least weekly, which surprisingly worked well for a small project. This approach allowed him to keep up with the rapid pace of development during Linux's early years.

The distribution of new tarballs continued until 2002, when Linux had grown into a much larger undertaking. At this point, Torvalds was still essentially working alone, relying on his own computer to manage the project.

He initially resisted adopting existing source-control tools because he wanted developers to work independently with their own local environments. This approach allowed them to focus on specific areas of development without being tied to a central hub.

As Linux's popularity grew and an expanding community of developers became involved in its growth, relying solely on Torvalds' manual patch application became unsustainable. The project needed a more efficient way to integrate contributions from multiple sources.

The introduction of the BitKeeper version control system brought significant improvements to the development process. Although its proprietary licensing created divisions within the kernel community, Torvalds credited it with making it easier to merge work from different subsystems.

Despite some developers' reluctance to use BitKeeper due to its licensing terms, Torvalds considered it a huge success in streamlining the integration of contributions. This marked an important step forward in Linux's development process, enabling more efficient collaboration among developers.

The Linux kernel's evolution has been marked by several significant changes over the years. One such change was the introduction of source control, which allowed multiple developers to collaborate on the project simultaneously. This marked an important step forward in the development process, enabling more efficient collaboration among developers.

However, this tool wasn't without its flaws. Linus Torvalds himself acknowledged that it had its shortcomings and helped him identify what he actually wanted from a version control system. The tool was also not mandatory for all maintainers to use, allowing for flexibility within the community.

The introduction of source control paved the way for other changes in the Linux kernel's development process. However, one major disruption came in 2005 with the BitKeeper licensing dispute. This forced Torvalds to seek an alternative version control system.

In response to this challenge, Torvalds developed Git, a new tool that would become the cornerstone of modern software development. The early versions of Git were not without their rough edges, and some developers found them unfamiliar, particularly those accustomed to CVS.

Despite initial reservations, Git's popularity soon grew, and today it is the de facto standard for version control. According to a 2022 Stack Overflow Developer survey, nearly 94% of respondents use Git, with almost 97% of professional developers relying on the tool.

The success of Git has been a remarkable development in the world of software engineering, with its impact extending far beyond the Linux kernel community. However, it's worth noting that Torvalds' initial intention was simply to create a tool for managing the Linux codebase, not to revolutionize the way developers work.

The traditional development model for Linux was marked by a slow pace of releases, with work piling up in the development tree while distributions backported desired changes into stable kernels. This led to long delays between intended annual releases, making planning and coordination challenging.

In response, Linus Torvalds proposed a significantly shorter release cycle, which initially met with skepticism from other developers. They reacted as if he had suggested something extraordinary, with some even questioning his sanity.

However, Torvalds' vision ultimately prevailed, settling into a nine-to-ten-week rhythm that has become the norm for Linux development over the past 20 years. This new model has enabled the creation of a remarkably stable and working operating system.

The focus on rapid, incremental improvements remains at the heart of Linux's development goal, with Torvalds emphasizing the importance of steady progress over dramatic feature launches.