Why Git Overtook SVN and Mercurial: The Rise of Distributed Version Control

In January 2024, GitHub announced that it will remove Subversion (SVN) support from both GitHub.com and GitHub Enterprise Server, ending the service that once hosted the world’s largest SVN repositories.

1. GitHub Says Goodbye to Subversion

GitHub introduced SVN support in 2010 when centralized version control systems were still dominant. Over the past 13 years, Git has become the de‑facto standard, with about 94% of developers using it, while SVN usage has sharply declined. GitHub reports that only around 5,000 repositories receive SVN requests each month, representing just 0.02% of all requests.

Co‑founder Scott Chacon joked on Twitter that the “April Fool’s post” announcing full SVN support on GitHub was the best ever, and now the feature is finally being retired.

2. Why Git Became the Sole Survivor

The 2022 Stack Overflow Developer Survey shows Git holding roughly 94% market share for version control, far ahead of SVN and Mercurial.

Historically, Subversion (SVN) offered a centralized, client‑server model where changes were stored on a central server before being pushed upstream. It was an open‑source alternative to commercial systems like Perforce and was widely adopted by small teams and companies.

Apache Subversion

SVN’s centralized approach became less attractive as software development shifted toward multiple independent teams and distributed workflows. Experts note that SVN’s reliance on a constantly available server and cumbersome branching model hindered agility.

Developers also criticize SVN’s handling of branches and its inability to delete them cleanly, whereas Git’s lightweight branches are easy to create and remove.

Mercurial

Mercurial, launched in 2005 alongside Git, gained traction in large enterprises such as Mozilla, Facebook (for Rust), Google (in its Piper system), Nokia, and Jane Street. Its strengths include excellent scalability for massive monorepos, a Python‑based implementation that offers portability, and a powerful extensibility system.

Despite a dedicated community, Mercurial remains a niche tool compared to Git’s overwhelming adoption.

Why Git Wins

Git’s dominance stems from a strong platform ecosystem (GitHub, GitLab, etc.), early adoption by the Linux community, and a massive contributor base that drives rapid feature releases. Git’s configuration commands are more user‑friendly, and its integration with file systems makes it a natural fit for most workflows.

While Mercurial still excels in certain large‑scale scenarios, Git’s continuous improvements (e.g., Git v2.38, Scalar) are narrowing those gaps.

In summary, Git has become the primary version‑control system because of its distributed model, vibrant community, and extensive tooling, while SVN has faded and Mercurial remains a specialized alternative.