Fundamentals 9 min read

What Linus Torvalds Reveals About Git’s 20‑Year Journey and Future

In a reflective interview marking Git’s 20th anniversary, Linus Torvalds discusses the system’s origins, design goals of performance, data integrity and distributed workflows, its unexpected rise through web developers, the evolution of hash algorithms, and his hopes for the next generation of version‑control tooling.

21CTO

May 10, 2025

What Linus Torvalds Reveals About Git’s 20‑Year Journey and Future

Twenty years ago, Linus Torvalds created Git, a distributed version‑control system, and made the first commit on April 7, 2005. To celebrate the anniversary, GitHub organized an interview with Torvalds.

Evolving Dynamics

Torvalds did not expect Git to remain relevant after two decades, but it became the dominant tool for source‑code management because it met developers’ needs for speed, data‑loss protection, and distributed workflows.

He notes that early adoption was slow; however, in 2008 many web developers began using Git en masse, especially after the rise of Ruby on Rails, which surprised him.

2005

Torvalds recalls his early talks at Google in 2007, where he praised BitKeeper for its coordination and merging capabilities and admitted that Git’s design borrowed many ideas from BitKeeper.

He emphasized three core design goals:

Performance: Large projects like the Linux kernel could not tolerate the 30‑second patch processing time of other tools.

No data loss: Using SHA‑1 hashes was a pragmatic choice to detect corruption, not a security feature.

Support for distributed workflows: Making repository copies simple and identical was essential.

Torvalds also expressed regret over the SHA‑1 choice, noting the confusion caused by supporting both SHA‑1 and SHA‑256. In 2020 Git was refactored to support multiple hash types, including SHA‑256.

Thanking Junio

Torvalds credits long‑time maintainer Junio Hamano as the true hero of Git’s success, stating that after 20 years one should talk to Junio rather than him.

He shares personal anecdotes, such as using only three Git commands (git version, git blame, git log) and hopes for more unified error‑tracking across hosting platforms.

Conclusion

Torvalds reflects that while Git has not fundamentally changed how programmers write code, it has simplified collaboration and made one‑off projects easier to share. He remains open to new challenges but does not foresee a new project that could replace Git’s role.