Mercurial, 20 years and counting: how are we still alive and kicking? [video]
A FOSDEM talk delves into Mercurial's unexpected 20-year survival, challenging the narrative that it's a 'dead' Distributed Version Control System (DVCS). This story resonated with HN readers, many of whom fondly recall choosing Mercurial over Git for its technical merits and user-friendliness in the early 2000s. The discussion explores lessons from this 'platform war,' contrasting Mercurial's elegant design with Git's eventual market dominance.
The Lowdown
The FOSDEM talk "Mercurial, 20 years and counting: how are we still alive and kicking?" investigates the enduring presence of the Distributed Version Control System (DVCS) Mercurial, an open-source project initiated in 2005.
- Despite being widely perceived as obsolete due to Git's overwhelming market dominance in the 2010s, Mercurial has maintained continuous development, contributed to modern tooling, and inspired new VCS projects like Sapling and jj.
- The presentation aims to deconstruct this paradox, exploring Mercurial's historical trajectory, its community dynamics, core technical aspects, and the influence of large corporations on its evolution.
- Key areas of inquiry include Mercurial's resilience against the "Git storm," its subtle impact on developer workflows, and the factors attracting new users to the system in 2025.
The talk ultimately leverages insights from Mercurial's past to forecast future trends in version control and reaffirm the enduring relevance of community-driven open-source initiatives.
The Gossip
Mercurial Memories & Missed Opportunities
Many commenters expressed a sense of nostalgia and often a touch of regret over Git's victory, recalling their early decisions to adopt Mercurial. They frequently cited Mercurial's technical superiority and user-friendliness as the primary reasons for their choice, highlighting the tension between a technically 'better' product and its market adoption.
Mercurial's Malleable Mental Model
A core theme centered on Mercurial's perceived simpler and more coherent mental model compared to Git. Users felt Mercurial's operations were more intuitive, making it easier to understand and manipulate the timeline. Some argued that Git, while powerful, often forces users to grapple with its internal complexities rather than offering a truly more capable, higher-level interface.
Git's Goliath vs. Mercurial's Pythonic Plight
Discussion also veered into the reasons behind Git's eventual market dominance. Commenters pointed to potential drawbacks of Mercurial, such as its Python implementation leading to perceived performance issues and a lack of a stable programmatic API. These factors are contrasted with Git's C-based core and the rapid evolution of its ecosystem, which some argue gave it an edge.
Continuing Cult Following & Modern Relevance
Despite its reduced mainstream presence, Mercurial maintains a dedicated user base. Commenters shared instances of still using it for personal projects, on low-power devices, or because they simply prefer its workflow and associated tools like TortoiseHg. The re-emergence of classic resources like hginit.github.io was also noted with appreciation.