Version Control Second Coming
A version control veteran proclaims a 'second coming' for the industry, driven by the demands of AI agents and a growing desire for alternatives to GitHub. The author details numerous emerging systems addressing challenges like massive monorepos and high commit rates, believing the space is finally innovating after two decades of Git's dominance. This piece resonates on HN as it taps into developer frustrations with Git and offers a technical glimpse into a potentially transformative future for a foundational technology.
The Lowdown
Pablo Santos Luaces, a seasoned version control expert known for co-founding Plastic SCM and advising on large monorepos, heralds a new revolution in version control, drawing parallels to Git's disruptive emergence in 2005. He posits that two major forces—the exponential increase in commit pace due to AI agents and a burgeoning movement to challenge GitHub's long-standing supremacy—are catalyzing this "second explosion" in the field.
Key takeaways from his extensive career and analysis of the current landscape include:
- Historical Perspective: Santos Luaces recounts his journey through various VCS systems (VSS, Clearcase, Subversion, Perforce) and the "first explosion" that saw Git triumph after the Bitkeeper controversy, acknowledging its revolutionary impact.
- Challenging GitHub's Reign: While recognizing GitHub's immense influence, he suggests its dominance is no longer unchallenged, comparing its potential fate to SourceForge's decline.
- The New Contenders: He introduces a wave of new or re-envisioned version control solutions:
- Entire: Founded by a former GitHub CEO, focusing on provenance tracking for AI-generated code and performance enhancements.
- Pierre (code.storage): A Git forge optimized for "AI scale" to handle massive commit and pull request volumes.
- Origin: The author's current workplace, dedicated to pushing Git's performance boundaries.
- GitButler: A client-side solution emphasizing improved user experience with features like stacked branches and "virtual branches."
- East River Source Control (ersc.io): Built on Google's Jujutsu, offering advanced concepts like versioning unsolved conflicts.
- Diversion: A cloud-first, non-Git system tailored for extremely large monorepos (e.g., >1TB) and centralized workflows, particularly for game development.
- Oxen.ai: Specializing in version control for large AI datasets.
- Lore (Epic Games): An open-source, non-Git, full-stack solution for gaming's large monorepo challenges, with efficient binary handling.
- Future Predictions: Santos Luaces anticipates radical changes, including the emergence of solutions for super-large monorepos and hyper-fast commit speeds. He predicts a "fall of distributed" models for very large repositories, favoring cloud-first or centralized approaches, and a resurgence of virtual file systems (VFS) despite current technical hurdles.
He concludes with profound enthusiasm, asserting that after two decades of relative stagnation, the version control domain is finally undergoing a vibrant period of innovation. Driven by the demands of AI and massive data, he believes it is the "best time in twenty years" to be shaping the future of version control.
The Gossip
Git Grit & General Grievances
Commenters largely split on the article's premise of a 'second coming' for version control. Many expressed skepticism, questioning if the new solutions truly address fundamental problems or merely re-engineer existing ones, often defending Git's functionality while acknowledging its flaws. Others, however, strongly agreed with the idea of a needed revolution, articulating their frustrations with Git's perceived stagnation and highlighting its shortcomings compared to commercial or proprietary systems like Mercurial, SVN, or Google's internal solutions. The debate often centers on whether Git was a net improvement over its predecessors or if its widespread adoption stifled innovation.
Virtual Visions & Monolithic Marvels
The author's predictions regarding the resurgence of virtual file systems (VFS) and specialized solutions for enormous monorepos garnered significant attention and approval. Many commenters echoed the sentiment that Git struggles with binary files and massive repositories, advocating for VFS as a superior approach. Discussions frequently referenced historical examples like Plan 9 and ClearCase as pioneers of powerful VFS models, detailing how these systems enabled flexible and efficient handling of complex environments and large datasets, in stark contrast to Git's limitations for such use cases.
AI's Agentic Ascent
The article's core thesis—that AI agents are fundamentally changing version control requirements—sparked discussion on how this new paradigm influences development workflows. Commenters explored how AI's high-volume, automated commits could shift the focus from user-friendliness to sheer efficiency and throughput, potentially exposing bottlenecks in systems like GitHub. Some were skeptical of the need for entirely new schemas or 'provenance tracking' for AI-generated code, arguing that existing version control concepts suffice. Others connected the potential decline of GitHub to Microsoft's reliability issues and broader concerns about corporate influence on open-source projects amidst AI's rise.
Critiques on Clarity & Content
A notable portion of the comments criticized the article's structure, length, and readability. Several readers expressed frustration at the perceived lack of a clear thesis or concise summary, indicating that they gave up reading partway through. This led to a meta-discussion about modern attention spans versus the value of long-form content, with some defending the article as a valuable overview despite its length, while others unequivocally deemed it poorly written and not worth the investment of time.