News for hackers. Stuff that matters.
Re:We've raised $17M to build what comes after Git by jgauth on Friday April 10, 2026 @02:35AM (#47714366)
Makes sense to me. The new coding agents are drastically changing software development, and I think there's a lot of space for innovation in how version control tooling works in this new world.
Re:We've raised $17M to build what comes after Git by progx on Friday April 10, 2026 @03:13AM (#47714657)
Why should ai need this? A linear backlog is enough, a cache, for everything else they can create it new in a short time.
Re:We've raised $17M to build what comes after Git by jcfrei on Friday April 10, 2026 @04:39AM (#47715252)
Another commenter explained it: It's about working on multiple branches in parallel. You can only check out one branch at a time currently in git - but with "but" you have all the changes just in memory so different agents can work on different branches at the same time.
Re:We've raised $17M to build what comes after Git by leadingthenet on Friday April 10, 2026 @05:56AM (#47715759)
git-worktree has been a thing for a decade+ and AI agents seem to be using them just fine in my experience. This is a solved problem.
Re:We've raised $17M to build what comes after Git by dbbk on Friday April 10, 2026 @08:20AM (#47716991)
That's not even true
Re:We've raised $17M to build what comes after Git by maerF0x0 on Friday April 10, 2026 @10:51AM (#47719032)
Why not? Are you considering git worktrees?
Re:We've raised $17M to build what comes after Git by dbbk on Friday April 10, 2026 @01:49PM (#47721459)
Exactly, worktrees solve this problem, every "agentic IDE" uses them
Re:We've raised $17M to build what comes after Git by jlokier on Friday April 10, 2026 @11:52AM (#47719986)
Working on multiple branches in parallel is literally what Git was created for, and how it's been used since the very first version 20 years ago.

Other commenters mentioned worktrees, which let you check out different branches at the same time from a single local repo. That's convenient, but not required.

Git always supposted "fast cloning" local repos as well. You just "git clone" from one directory to another. Then they are indepedendent and you're free to decide what to merge back.

These days, agents can also fork their containers or VMs as often as required too, with copy-on-write for speed.

So that's four ways to work on multiple branches in parallel using Git that we already use.