What could replace Git for collaborative coding?

TL;DR

Git is foundational but not flawless; new approaches like Delta DB aim to turn an IDE into a collaborative workspace while remaining compatible with Git. The rise of AI collaborators highlights the need for simpler, more intuitive version control and better team workflows beyond traditional merges and rebases.

Transcript

It's genuinely hard to overstate how important Git is to modern software. It's essential to the entire ecosystem that we all build in and love. Open source would not be what it is today without Git. Platforms like GitHub would not be viable without Git. Work at companies would be obnoxious if every single company was using their own weird version c... Read More

Key Insights

• Git is essential to modern software but has UX and workflow friction that can impede collaboration. The argument for improvement centers on reducing cognitive load and making source control invisible to focus developers on coding.
• Delta DB is introduced as a collaborative workspace that could replace Git while remaining compatible, signaling a deliberate move toward new paradigms that integrate discussion, intent, and history inside the IDE.
• Zed IDE received significant backing from Sequoia, illustrating investor confidence in fresh, AI-aware development tools that address the coupling of AI agents with codebases.
• AI involvement in coding complicates traditional Git workflows, creating pressure for tools that can manage changes and collaboration when contributors may not be fully versed in version control best practices.
• The historical arc from SVN and BitKeeper to Git shows how collaboration needs evolved, ultimately favoring distributed graphs and pull request workflows that Git popularized through GitHub.
• Conversations about how to merge work and coordinate tasks often dominate developer time, highlighting the desire for source control to guide actions automatically rather than require manual decision making.
• The push for a centralized truth in collaboration remains strong, with GitHub serving as the focal point for many teams, even as debates about the ideal structure and UX continue.
• WorkOS sponsorship is framed as easing enterprise setup, illustrating how tooling ecosystems are seeking to simplify adoption and administration across large organizations.
• More videos from this channel:
  • How to use Gemini CLI open source AI tool
  • What is MCP and how can Anthropic fix it?
  • How to avoid fetch on render in React data fetching
• More from this channel: Theo - t3․gg

Questions & Answers

Q: What is the main reason people think Git may not be the best solution for today’s teams?

The core argument is that Git has a complex user experience and workflow that forces developers to spend time on merge and rebase decisions rather than programming. This friction reduces productivity and shifts focus away from writing code to managing source control, which many see as a failure of the tooling to disappear into the background.

Q: How does Delta DB relate to Git according to the video?

Delta DB is presented as a vision for turning an IDE into a collaborative workspace that can function as an alternative to Git. It aims to preserve compatibility with Git while offering a more integrated, discussion-driven approach to code changes, making collaboration more seamless and context-rich.

Q: Why is Zed IDE mentioned, and what happened with its funding?

Zed IDE is highlighted because it is a new editor designed for a better coding experience and is embracing AI. Sequoia backed Zed with $32 million, signaling investor interest in modern, AI-aware tools that rethink how code is written, reviewed, and integrated with Git.

Q: What historical context does the speaker give about version control tools?

The speaker traces lineage from SVN and BitKeeper to Git, explaining how the open source model and collaboration needs evolved. Git emerged to address chaotic patch workflows and email-based contributions, eventually enabling distributed collaboration and GitHub style pull requests that standardized the workflow for many teams.

Q: What problem with Git does the Casey Moratori discussion illustrate?

The discussion argues that the real problem is not the code itself but the overhead of deciding how to merge or rebase, which distracts developers from programming. It emphasizes that source control should guide correct processes automatically, reducing the cognitive burden on engineers.

Q: Why is there a push to hide source control in the background, according to the speaker?

There is a belief that source control should facilitate programming without requiring constant attention to the mechanics of version control. If implemented well, it would automatically coordinate actions, email notifications, and scheduling, letting developers focus on building software rather than manipulating branches and histories.

Q: What role does GitHub play in the current software development ecosystem, as described?

GitHub is described as central to collaboration, providing a platform for pull requests, comments, and merged workflows that transformed how teams contribute to open source and larger projects. It created a centralized truth and a familiar workflow that many developers rely on daily.

Q: What does the speaker imply about AI contributions to coding and its impact on Git?

AI contributions complicate traditional Git workflows because non-traditional contributors may push code changes without fully understanding version control. This accelerates the need for smarter tooling that can manage changes, discuss context, and ensure coherent collaboration without bogging down developers with Git specifics.

Summary & Key Takeaways

• Git is foundational yet imperfect, prompting exploration of new collaborative tooling and IDE-centric workflows that aim to simplify how teams coordinate changes.

• Delta DB represents a venture to replace Git without breaking compatibility, signaling a shift toward integrated collaboration directly inside development environments.

• The ecosystem around Git evolved from centralized and distributed models to centralized platforms like GitHub, which popularized pull requests and improved collaboration at scale.