> The old model assumed one person, one branch, one terminal, one linear flow. Not only has the problem not been solved well for that old model, it’s now only been compounded with our new AI tools.

A bit of a strange thing to say in my book. Git isn't SVN and I think these problems are already solved with git. I agree that the interface is not always very intuitive but Git has the infrastructure which is very much focused on supporting alternatives to "one person, one branch, one terminal, one linear flow".

> the problem that Git has solved for the last 20 years is overdue for a redesign.

To me it's not clear what the problem is that would require a redesign.

- leads with amount of money raised - mentions a16z - i use git every single day and have no idea what exactly the thing will do

they aren't building something to help you, they're building something to trap you. even if it's free, does things you like, etc., do not use it. their end goal is to screw you

The tool that could replace git must free, ubiquitous, and arguably open-source. This is why I cannot imagine how raising $17M may pay for itself in that case, to say nothing of a 10× return.

It may be a great tool, but I'd be very reluctant to use a closed-source solution as a cornerstone of infrastructure.

A lot of people seem confused about how they raised the money, but it’s actually a pretty easy VC pitch.

- It’s from one of GitHub’s cofounders.

- GitHub had a $7.5B exit.

- And the story is: AI is completely changing how software gets built, with plenty of proof points already showing up in the billions in revenue being made from things like Claude Code, Cusor, Codex, etc.

So the pitch is basically: back the team that can build the universal infrastructure for AI and agentic coding.

I recently switched to Jujutsu (jj) and it made me realize that “what comes after Git” might already exist.

It turns out the snapshot model is a perfect fit for AI-assisted development. I can iterate freely without thinking about commits or worrying about saving known-good versions.

You can just mess around and make it presentable later, which Git never really let you do nicely.

Plus there’s essentially zero learning curve, since all the models know how to use JJ really well.

Installed GitButler to try it out — and realized it installs malicious Git hooks to take over the git commit workflow:

* pre-commit — The malicious one. It intercepted every `git commit` attempt and aborted it with that error message, forcing you to use `but commit` instead. Effectively a commit hijack — no way to commit to your own repo without their tool.

* post-checkout — Fired whenever you switched branches. GitButler used it to track your branch state and sync its virtual branch model. It cleaned this one up itself when we checked out.

* There's also typically a prepare-commit-msg hook that GitButler installs to inject its metadata into commit messages, though we didn't hit that one.

* The pre-commit hook is the aggressive one — it's a standard git hook location, so git runs it unconditionally before every commit. GitButler installs it silently as part of "setting up" a repo, with no opt-in. The only escape (without their CLI) is exactly what we did: delete it manually.

Those who don't understand git are bound to reinvent it. Git is fine as it is, with some porcelain and QoL improvements here and there. Some of the most capable devs I know use git + cgit for collaboration and they manage just fine.

I personally feel that:

1) Git is fine

2) I would not want to replace critical open source tooling with something backed by investor capital from its inception.

Sure, it will be “open source “, but with people throwing money behind it, there’s a plan to extract value from the user base from day one.

I’m tired of being “the product”.

Critical open source tooltips by should spring from the community, not from corporate sponsorship.

First off, I'm of course interested to see what the future infrastructure of software building next looks like.

> The hard problem is not generating change, it’s organizing, reviewing, and integrating change without creating chaos.

Sure, writing some code isn't the bottleneck. Glossed over is the part where the developer determines what changes to make, which in my experience is the most significant cost during development and it dwarfs anything to do with version control. You can spend a lot of energy on the organising, reviewing, patching, etc. stuff -- and you should be doing some amount of this, in most situations -- but if you're spending more of your development budget on metaprojects than you think you should be, I don't think optimising the metatooling is going to magically resolve that. Address the organisational issues first.

> This is what we’re doing at GitButler, this is why we’ve raised the funding to help build all of this, faster.

The time constraint ("faster") is, of course, entirely self-imposed for business reasons. There's no reason to expect that 'high cost + high speed' is the best or even a good way to build this sort of tooling, or anything else, for that matter.

Git's UI has become increasingly friendly over a very long time of gradual improvements. Yes, Mercurial was pretty much ideal out of the gate, but the development process in that case was (AFAIK) a world away from burning money and rushing to the finish.

Maybe going slow is better?

Why does it take $17m to beat Git?

How will you ever get the network effects needed to get sustained users with a commercial tool?

Given Git was created because BitKeeper, a commercial tool, pulled their permission for kernel developers to use their tool aren’t we ignoring a lesson there?

The only security incident I've had in my career was due to Git Butler - it committed temporary files into GitHub without me explicitly approving it! Of course, it was a private repository, but still, it became impossible to delete those secrets because there were plenty of commits afterward. Given the large file tree and many updated files in the commit, it wasn't apparent that those folders got sneaked into the commit.

So, I really hope security incidents don't come after Git!

Honest question. I love some of the additional capabilities and specifically the dependency commits, virtual branches, and JSON output...

BUT why not just work with the git community to add this functionality? It doesn't seem like the kind of thing that needs to "replace" git, as opposed to "improve" git?

"What comes after Git" looks inside

Git CLI with flowers and unicorns.

Is this what gets funded nowadays? I really hope for a gigantic mega crash of all the IT companies. This industry deserves it like none other.

To all the salty people- the person cofounded GitHub. It's not the product that raised 17M, it's the person.

For a long time I couldn't decide if Git Butler was a real product or a very elaborate joke to get devs to type "but rub" into their terminal.

https://docs.gitbutler.com/cli-guides/cli-tutorial/rubbing

I like their vision, though, this is compelling to me:

> What if it was easier to for a team to work together than it is to work alone?

It generally _is_ easier to work alone with git. UI and DX experiments feel worthwhile. lazygit and Magit are both widely used and loved, for example, but largely focus on the single user experience.

I actually believe we need to rethink Git for modern needs. Saving prompts and sessions alongside commits could become the norm for example, or I could imagine having different flags for whether a contribution was created by a human or not.

This doesn't seem to be the direction these guys are going though, it looks like they think Git should be more social or something.

Nowadays I just ask my LLM butler to "organize outstanding changes into coherent commits". No new software needed.

The remaining lifetime of a technology is proportional to how long it has already existed.

However good this new thing might be, however much better it might be than git - I don't like it's chances.

I like what I see in the video, it would solve a lot of problems I end up having with git.

That said, I find the branding confusing. They say this is what comes after git, but in the name and the overall functionality, seems to just be an abstraction on top of git, not a new source control tool to replace git.

Genuinely curious about the collaboration model here. Git's biggest weakness isn't technical — it's that merge conflicts are a social problem disguised as a technical one. Two people editing the same file usually means the ownership boundaries are wrong, not that the VCS is.

What does "what comes after Git" look like for a two-person team vs. a 200-person org? The pain points are completely different.

The source code is hosted on Github: https://github.com/gitbutlerapp/gitbutler

I was really hoping we'd see some competition to Github, but no, this is competition for the likes of the Conductor App. Disappointed, I must say. I am tired of using and waiting for alternatives of, Github.

The diff view in particular makes me rage. CodeMirror has a demo where they render a million lines. Github starts dying when rendering a couple thousand. There are options like Codeberg but the experience is unfortunately even worse.

The amount of ~skepticism~ hate is astounding here!! People don’t even acknowledge that it’s written in RUST!!!!

Seems fine I guess. I'm not a fan of Perforce but it does have some features that git still struggles with and needs to address to break into new customers. This Gitbutler seems to address some of them but I can't say it really feels next gen.

I like the idea of parallel branches. I feel like you could probably get away with just creating multiple, named stages but having a full history is nice. P4 has multiple pending CLs and it works nicely enough. This sounds a bit better so that's cool.

As far as "social coding" git's design is really at odds with any sort of real time communication. I would love to see a first class support for file locking, and file status work flows. It's not big at all in code dev because code can be merged but for non-coders, source controlled assets are often not mergeable. To solve this, P4 is often used with heavily integrated tools that provide live file status (Locked, out of date, edited by others). This way merge conflicts are prevented at author time. Git is really lacking here. Is fetching constantly really the best we can do?

Then of course... can we get some large file and partial checkout workflows that don't feel good?

I thought git didn’t allow companies to use git in their name any more and grandfathered in girhub, gitlab, etc. How did this company get a trademark.

Also, I don’t think I would use this and the problems they describe aren’t really things I care much about.

I wish them the best, but $17m on a devtools company that thinks they are replacing git is going to be rough going.

Real question--- why does one of the GitHub co-founders need to raise 17M for a venture? I'm certain they could fund it themselves. Is this more or less a marketing play than anything else?

Git just works. If you're not really familiar with it, you can use a free UI. If you don't know anything about it, AI like ChatGPT or Claude can help you commit or even teach you Git.

If you raise money for this project, you probably intend to make money in the near future. I don’t think anyone here wants ads on Git or to argue with a manager to get the premium version of GitButler just because you reached the commit limit.

These $17M should go to the Git maintainers.

> Imagine your version control tool taking what you’ve worked on and helping you craft logical, beautiful changes with proper context

This is actually really important/useful, it's just not apparent to people who haven't worked on AI agents.

AI agents do a lot of work under the hood to try to save your tokens. There are two basic methods: 1) semantic knowledge maps, 2) PageRank. Agents like Aider will build a semantic knowledge graph of your codebase - the files in it, the functions, variables, etc - so that it can tell the agent exactly where everything is in a tiny summary. It'll also then use PageRank to build a graphed rank of these things, to surface the most relevant items first. (https://aider.chat/2023/10/22/repomap.html)

A modern VCS could do all of these things for you too, and the result should be making it easier to work with code, pulling in the related context simultaneously, so your changes make sense.

I don't have to read the article to know that if it not just git with fixes and new features, it's not going to pan out. This is like building a new house because your current house needs a couple of leaks fixed and a coat of paint.

Claims about “what comes after git” aside, I really like the idea of virtual branches. Worktrees have a pitfall IMO that they don’t allow you to test changes in a running local env, meaning I need to commit the changes, close the worktree, and checkout the branch on my primary workspace to verify.

Gitbutler virtual branches OTOH appear to provide branch independence for agents/commits, while simultaneously allowing me to locally verify all branches together in a single local env. This seems quite a bit nicer than checking out worktree branches in the primary workspace for verification, or trying to re-run local setup in each worktree.

i dont get it, watched the video seeing the "power" of using multiple branches at the same workdirectory etc. all i was thinking was ok they want to make it easy for coding agents work with multiple branches / feautres at once... Just that works already pretty well with git and worktrees... and agent uses the tools anyway... dont know what they want to build with 17M

Maybe the pitch is:

git is distributed. Decentralised improvement. Local computers and their users make changes. These steps of local added value are then centrally combined into a shared timeline. A single product. During the improvement the locus of control is local. Which means it is hard to harvest the knowledge of this local knowledge and replace it. And it's hard to make local users serve the central AI.

Not something you put in the public mission statement. Because you might get boycotts.

I failed to see why this would be something that "comes after Git" from a VCS perspective.

The line-based diff(1)/diff3(1)/patch(1) kit often works, and that mindset thrives and gets carried till today. Many toolkits and utilities have been designed to make it more ergonomic, and they are good. Jujutsu is an example. We also have different theories and implementations, some even more algebraically sound like Darcs and Pijul.

But GitHub the Platform is another story, given that they struggled to achieve 90% availability these days.

How I'm using git/Github has changed with agentic coding. However, I'm not using swarms of agents to write code, so it's bit hard for me to decipher the JTBD of gitbutler.

Another take I've seen is https://agentrepo.com/, which is light-weighted hosted git that's easy for agents to use (no accounts, no API keys, public repos are free). There are large parts of the GitHub experience I'm no longer using (mostly driving from Claude), so I think this is an interesting take.

No shade on these guys, looks like a cool tool and I'll try it. However, I find myself doing large majority of my git operations using a an agent[1] or a TUI [2], and I rarely open a git interface. I can get everything done straight from the terminal.

I guess I can overcome the "what if I cannot undo" anxiety.

[1] https://getcook.dev [2] lazygit

I thought gitbutler was not a great name, but then I saw their CLI command name is "but"

My only issue is the title. It appears they are building a replacement for GitHub of which a replacement for Git is just a component. Building a replacement for GitHub is going to need at least the sort of funding they are mentioning. So once one reads the article it makes a bit more sense.

I do not understand the problem solution, but if anything with git, I would want Codeberg style. I moved to gitlab and they were soldout and I am back on github slowly transitioning out. Common sentiment I believe is we want git, but on our own terms, not another VC funded project to move in.

As long as this tool doesn't break "fast forward merge" and proper linear history and allows you do delete PRs unlike its GitHub progenitor then I'm happy.

I have found that a number of times GitHub's idea of "convenient" comes either from 1) not understanding git fundamentals such that it closes off possible workflows, or 2) pushing a philosophy on users, i.e. I know better than you, so I'm going to block you.

It’s weird because I could see raising money on the premise that GitHub is garbage, not git. But then you can’t say I co-founded GitHub as your bona fides.

Wow. So much hate in the comments here. Of all the funding / equity events lately, I wonder how this one gets so much doubt and distrust from the start.

If this isn’t something to at least root for, in the sense of a small team, novel product, serving a real need, then I dunno what is. You can use jj or tangled and still appreciate improvements to git and vcs on the web in general. Competition amongst many players is a good thing, even if you don’t believe in this one particular vision.

Heaven forbid it isn’t 100M going to a YC alum for yet another AI funding raise.

Jumping on the bandwagon, Magit is raising $$$ to Keep Version Control Magical https://github.com/magit/magit/issues/5555

Why are investors still investing in SAAS products like this? I've heard some investors made rather blunt statements about such investments being a very hard sell to them at this point. Clearly somebody believes differently here.

We have AI now. AI tools are pretty handy with Git. I've not manually resolved git conflicts in months now. That's more or less a solved problem for me. Mostly codex creates and manages pull requests for me. I also have it manage my GitHub issues on some projects. For some things, I also let it do release management with elaborate checklists, release prep, and driving automation for package deployment via github actions triggered via tags, and then creating the gh release and attaching binaries. In short, I just give a thumbs up and all the right things happen.

To be blunt, I think a SAAS service that tries to make Git nicer to use is a going to be a bit redundant. I don't think AI tools really need that help. Or a git replacement. And people will mostly be delegating whatever it is they still do manually with Git pretty soon. I've made that switch already because I'm an early adopter. And because I'm lazy and it seems AI is more disciplined at following good practices and process than I am.

jj is rapidly becoming the new standard for post-git VCS in my circles. I’d love to see more startups working on that.

Hey, this is Scott - the guy in the photo who wrote this post. AMA.

I'm trying to estimate how much better than git a new system would have to be to convince me to abandon git and learn the new system

I don't know the answer, but I think it could easily be three times as good and I would still stick with git

No CLI installer for Windows.

App itself for Windows won't proceed past my selected repo. Said something about bad permissions, but I use that repo every day.

Huh. I look at what it took to build Git to begin with[1] and have to wonder if the thing that comes after it is really going to be _that much_ better. Git came about because there was a need for it. I feel like GitButler came about because there was a need for funding. Maybe I just need to have my coffee before commenting.

[1] https://en.wikipedia.org/wiki/Git#History

Git isn't that old. I find it interesting people want to replace it by big money. Does this say something about the quality of git? Enough people also complain about that.

I'm reminded of a comedy album, "The First Family", from the 1960s where Bobby Kennedy impersonator wanted to form a new political party. He named it something like "Major Affiliate For an Independent America" (I might have that wrong.) Or the M-A-F-I-A.

He said their first order of business was to change the name of the organization.

https://www.youtube.com/watch?v=Xwu8S6Ekx9w

EDIT: I'm not positive that's the correct album but have a good laugh anyway.

X is hard to use because when something goes wrong you need to have a deep knowledge to figure it out! Let's build Y on top of X to make this easy! Now you just need to have deep knowledge of both Y and X to figure problems out. And it's gonna cost $17M to build Y. Deal?

I watched the demo video on the git butler home page and agree with the premises that:

1. git is not going away 2. git UX is not great

So i appreciate their effort to manage development better as agents make it possible to churn out multiple features and refactors at once.

BUT, I reject this premise:

3. Humans will review the code

As agents make it possible to do so much more code (even tens of files sucks to review, even if it’s broken into tiny PRs), I don’t want to be the gatekeeper at the code review level.

I’d rather some sort of policy or governance tooling that bullies code to follow patterns I’ve approved, and force QA to a higher abstraction or downstream moment (tests?)

What "comes after Git" is not a proprietary solution developed by a VC-backed company.

Doesn't jj basically do all this and more?

I wonder what the development of git itself has cost in engineer time? Presumably more than $17 million? Assuming a fully loaded engineer is 250k, that only amounts to 68 engineer-years over 20 calendar years, which seems low.

Anything that leads off with how much money you've raised is automatically disqualifying.

LLMs have solved the Git problem without any need for other tooling. There is no learning curve anymore. You don't need to know any commands or even look at the CLI. You can explain in plain text what you're trying to do.

That money could've gone to something useful instead of building "git but better"

The only thing I want is an as far as Claude Code can tell 100% Github clone running on my $5 Hetzner VPS.

Looks like almost as good as JJ but with VC money.

Remind me, how much venture capital did Linus need to raise for building git?

Makes sense. Git solved versioning, not collaboration at scale. Most real pain today is juggling context across PRs, tools, and now agents not writing code.

“raise 17m to try to kill off and extract value from popular open source tool”

Pound foolish and folly

Is this actually replacing git, or just a new frontend for the same git stuff? In any case, I'll be interested to see if this still exists in a year, and if that $17M actually made it replace git

Git is pretty close to ideal for the distributed model.

I think the real money is in figuring out a centralized model that doesn't suck. Explicitly locking things has certain advantages. Two people working on the same file at the same time is often cursed in some way even if a merge is technically possible. Especially if it's a binary asset. Someone is going to lose all of their work if we have a merge conflict on a png file. It would be much better to know up front that the file is locked by some other artist on the team.

Apparently what comes after git is git

I feel like we’re over-capitalizing a problem that could be solved with better protocols. If the "Git successor" is just a wrapper to help agents not hallucinate their own worktrees, it feels like a very expensive solution to a context-window management problem.

I was thinking- why on earth raise 17M for that, it sounds like something you make in a basement with a few friends, if that.

But then it's the github cofounder- well, github did add a lot of stuff onto git I didn't know I needed, so I'm curious.

The title is misleading and click bait perhaps.

But you also get an idea of the average reading skill of people based on the top 3 comments: "I don't want a replacement for Git!"

I'm not blaming anyone, or maybe both the readers and the authors.

People now write something that could've been published as a short story 30 years ago, for something that could be a paragraph in length, detailing their emotional state, minute background information, their hopes and dreams.

The adaptive response to this by humans and society is to read the headline and ignore the prose, as the prose is so god damn long.

"Gitbutler is a UI for Git" would've been more suitable than hype about replacing git.

jj is what comes after git.

It can back on to git if you want, so a migration doesn't have to be all-at-once. It already has all of these features and more. It's stable, fast, very extensible.

jj truly is the future of version control, whereas git plus some loosely specified possibly proprietary layer is not.

I'm excited to see what ersc.io produces for a jj hosting service and hopefully review UI.

Humm at a quick glance git was functional enough for the linux kernel after 2 people worked on it for 4 months. That doesn't really add up to 17M.

Some others mentioned pijul, but I will put in my two cents about it. I have been looking to make use of it because it seems really nice for working with an agent. Essentially you get patches that are independently and can be applied anywhere instead of commits. If there is ambiguity applying a patch then you have to resolve it, but that resolution is sort of a first class object.

I looked at the demonstration video and closed it after a couple of minutes. I don't see how this tool will replace git.

Well, I think it won't

This will just force them to build in some sort of revenue extraction model. Pass! Git and copyleft are fine as is.

They need to have a dedicated page explaining me why should I change my current workflow. Else I don't get the point.

Linus built git in an afternoon with $17 for snacks

I watched the video but I don't quite get it. I feel like I'm missing something? A nicer git workflow is not what I need because I can ask an LLM to fix my git state and branches. This feels a bit backwards. LLMs are already great at working with raw git as their primitive.

I'm curious what their long term vision they pitched investors is.

I love how whole article described none of the ideas they have for product, just buzzwords

The title mentions 'after git' but the video demo shows that it's very much tied to git and Github. The post also mentions the overhead of dealing with git, but the examples shown come with their own overhead and commands. I'm admittedly unable to see the appeal or just misunderstanding it, but the number of stars on the repo shows I'm in the minority.

I can't see any significant difference between their "Operations Log":

https://docs.gitbutler.com/cli-guides/cli-tutorial/operation...

and git's reflog:

https://git-scm.com/docs/git-reflog

I don't know about a new Git, but GitHub feels like the cruftiest part of agentic coding.

The Github PR flow is second nature to me, almost soothing.

But it's also entirely unnecessary and sometimes even limiting to the agent.

The initial version of Git was written in two weeks, what do you need $17m for?

How many millions were raised to build Git?

Most of the comments here are clearly from people who haven't used GitButler. Try it out and it's a very sticky product, clearly superior workflow to vanilla Git.

Is anyone from GitButler reading this?

As others alluded, JJ already exists and is a credible successor to Git for the client side.

Technical desides aside though: how is this supposed to make money for the investors?

Is $17M private equity enough to poison the initiative? Or is software-by-committee still the real project killer? Let’s find out…

I'd like to see some kind of "whitespace aware" smart diff in whatever comes after git

Dunno what they’re trying to build, but I encourage everyone to try what they already have built. It helps me work on multiple changesets in parallel. This often just happens, for example you work on something and discover a bug in something else that needs to be fixed. In GitButler, I can just create another branch, drag the changes in there, push and done.

Also, if you ever worked with Perforce, you might be familiar with changelists. It’s kind of like that.

Now, GitButler is by no means perfect. There are many rough edges. It tends to get stuck in unexpected states and sometimes it isn’t easy to rectify this.

It also cannot split changes in a single file, which is a bummer, because that’s something I encounter routinely. But I understand this complicates the existing model tremendously.

GitHub CEO also raised 60M for 'entire' to bring agent context to git. The dust is yet to settle here as it's difficult to bring a paridgm shift from today's git workflows

please also build it for easy multimedia management

Linus Torvalds was able to build this in a cave!

With a box of scraps!

First time I heard of gitbutler, is this like gitk? If anyone remembers gitk

"Gitbutler", really rolls off the tongue, doesn´t it :) Oh and the irony of raising $17M to "replace" a tool which kinda...does not need replacing at all? How about replacing some of the entshittified services, like Google Workspace? Now that would be worth the $17M raised.

I was skeptical at first, but then I watched the video and it really looks interesting. I wonder if this works with Azure DevOps?

How much money did they need to raise to make git?

Why this and not jujutsu, pijul or sapling? These are all version control systems that are better than git in various ways.

Great! Instead of solving actual problems we are seeing funding for stuff we don't need.

no mentions of dura by nobody in the comments?

Improving something that basically everyone uses is obviously worth money

How do you intend to make money ?

Easier Git doesn't translate into something I can get my boss to pay for.

Isn't that jj? Hopefully no one tells the VCs.

Meanwhile CVS just keeps working fine...

My impression from GitHub was always that it was nice to have someone else host Git repositories for free, and that the "added value" (the Web view, the user management, the CI, the Wiki) were all made by dilettantes: poor quality, mostly useless, never doing the right thing.

These people seem to think that their "added value" was the selling point of their product... they appear to believe that some bad things are actually good and desirable, like, for example:

> Heck, it could be argued that development in teams is less social than it was when version control was centralized.

> But what if coding was actually social? What if it was easier to for a team to work together than it is to work alone?

This reeks of open-space floor office plan all over again! When some HR managers decided that programmers need all to sit in the same room the size of a basketball court and that would somehow help them work together better...

Programming is absolutely an individual activity first, where communication helps, but in order to be helpful the communicating parties have to have an initial internal process that refines the messages s.a. not to waste the other party's time. In practice, productive communication may happen once a day... up to once a week maybe? Maybe even less frequently? Git, as it is, is perfectly fine for this.

> Ok, that’s the simple case, pretty straightforward. However, GitButler can also do some pretty cool things that Git either cannot do or struggles with, namely:

> Having multiple active branches that you can work on in parallel.

I'll check out the same Git repository in different directories and will have this ability... maybe also add the second checkout as a remote to the first... but the number of times I've done it in two decades of working with Git is... maybe two? This is an extremely unusual need. I think, I've done this when migrating from multiple repositories into a monorepo and I had to somehow reorganize the history of multiple repositories so that it would make sense together. Definitely not a task for every day, not even every year.

The whole follow-up demonstration of parallel branches is just... Why on earth would I ever want to do that? Why would I want to work in such a way that I commit changes to different branches at (roughly) the same time? It's kind of like stashing changes, but, stashing is the byproduct of "bad planning": I wanted to do one thing, and accidentally did another... oh well, let's save the change somewhere temporarily! But, ideally, I want this to happen as little as possible. Not because it's inconvenient to deal with stashed changes, but because I will very quickly lose track of what goes where, why any particular branch exists etc.

Similarly, for the stacked branches: I absolutely don't want this functionality to exist... if it was already in Git, I'd request that it never be used. This complicates the mental model of what is even possible in the repository and creates some nightmare fuel scenarios: what happens if you stack them sequentially? What happens if you stack many branches on the same branch, and then want to rebase one of the stacked branches? What happens if you rebase the branch on which other branches are stacked? What happens if you delete the branch on which other branches are stacked? Does the stacked branch have to exist in the local checkout, or could it come from a remote?

It's absolutely the case where simple is better (I'd never imagine I'd call Git simple, but here we are).

I can't imagine what the workflow of people who want these changes must look like. I can't imagine why would anyone want to copy that kind of a workflow.

A lot of blood in the water for Github.

There's definitely a need for this, but the underlying reason there's a need for this is so beyond me. I've worked with a lot of Software Engineers over the years, even at FAANG, that didn't have a good technical understanding of git (basically, your repo is a tree structure, most commands are just about manipulating that tree in some way). I mean, just spend the hour to go through a git tutorial. There's so many great ones like the interactive one that shows the tree as you go through the levels. It's your profession. Also, I think another layer on top of Git as this seems to propose won't fix it -- once something non-obvious happens, these people continue to be stuck.

But… why? (pun intended)

They raised $17M to build what appears to be solvable by some git wrapper scripts that could have been written by AI in 5 minutes?

To me the extra "wat" about this is that if I spend the sub-$1 to get the git wrapper scripts, I can get them exactly the way I want them, instead of being mandated to use the commands they made up. A huge gain for AI is the ability to have exactly the software you personally want, even if nobody else wants it just so.

So they are building the exact opposite of the need that AI brings forward. What they are building is not even median software that is in danger of being replaced (e.g. see Cloudflare spending a week to build "a wordpress"), but something that's the most extreme example of AI-will-replace-this that could possibly exist.

Who will buy this?

The only way this makes sense is as a plea for being acqui-hired (and the project dropped).

Rather confusing, your name has Git in it, “to build what comes after git”, what comes after your own Git product? Good luck.

Jesus this website is overstimulating and it's extremely difficult to understand. What the hell they are selling other than a UI on top of Git? Git works perfectly fine especially if you take an hour or two to learn how to do a few more complicated but useful workflows (rebasing, cherry-picking).

Wow, very impressive, great job! You mentioned monitoring, I think it might be a very interesting way to see the "ongoing" work of your agents and orchestrate them. Do you have a precise idea on how it's going to happen, or is this already planned?

For $17 milion there are few thibga without any gui that i couldnt build.

> I know what you’re thinking. You’re hoping that we’ll use phrases such as “we’re excited,” “this is just the beginning,” and “AI is changing everything”. While all those things are true

Superbly tone deaf. The only people who might possibly want to read that are those already drinking your Kool-Aid, most everyone else can already smell the bullshit.

Blog post written by llm.

No thanks.

Was their series A pitch also written by llm?

If you're building on top Git, you're not really coming after it are you - you're coming as well as it.

If you want to come AFTER Git... you need to not use Git.

From their docs:

> We are creating not only a new kind of Git client,

Nope, not going to be the tool of the future.

The fundamental problem is it is still based on git.

Till this addresses submodules and makes them a first class citizen it's just tooling on top of a VCS that still ONLY supports single project thinking.

gitbutler is actually a great product tbh

> I may have even had a small hand in some part of that.

Quite an understatement. I'm pretty sure GitHub is the primary reason that Git took off like it did.

Ok, ok, if you give me $16M I'll do it faster.

> Imaging being able to work on a branch stacked on a coworkers branch while you’re both constantly modifying them

I think that's something I don't want to imagine

The title is misleading, it's not a git replacement

Raising a bunch of money to recreate the wheel.

I'm still not convinced we need a replacement for git.

> The old model assumed one person, one branch, one terminal, one linear flow.

Um, there's more than one flow out there? Feature branches are usually "one person, lots of branches, squish at the end". Since when is Git linear? Some of them even come with their own scripts or GUIs.

I'm even less convinced that something that's raised $17M already will provide a free-as-in-beer solution.

Github fallout effect?

That's a lot of money for something very much not necessary... I'm in the wrong business!

Nothing needs to come after git. its perfect.

I like pijul's mental model much more but it's a single developer who's slightly prone to getting sidetracked.

You could have given Linus the weekend off.

> We've raised $17M to build something like git and bait-and-switch it later because VCs only exist to extract value and anything we end up building will be a shadow of a fart of how useful git actually is

FTFY. I don't understand how anyone could think to replace git by raising money. The only way to truly do this is grassroots iteration. You can build the software, but the distribution will never reach the same network size as git before your investors start asking "When do I get my return?"

> Imagine your tools telling you as soon as there are possible merge conflicts between teammates, rather than at the end of the process.

So you're centralizing a fully distributed process because grepping for "<<<<<<<" and asking your teammate the best way to merge is too hard? I thought coding was supposed to be social?

I mean, honestly, go for it and build what you want. I'm all for it! But maybe don't compare it to git. It's tone deaf.

There is only a tiny final step left, a real piece of cake, to build the thing.

Pijul?

Git has issues, but it works pretty well once you learn it and it's basically universal. Will be hard to dislodge.

$17m to replace git with but. no fucking way

$17M doesn't seem like enough for this. Perhaps for a prototype.

I started using Git around 2008, if memory serves. I have made myself more than familiar with the data model and the "plumbing" layer as they call it, but it was only a year ago -- after more than two decades of using Git, in retrospect -- that a realisation started downing on me that most folks probably have a much easier time with Git than I do, _due_ to them not caring as much about how it works _or_ they just trust the porcelain layer and ignore how "the sausage is made". For me it was always either-or situation -- I still don't trust the high-level switches I discover trawling Git's manpages, unless I understand what the effect is on the _data_ (_my_ data). Conversely, I am very surgical with Git treating it as a RISC processor -- most often at the cost of development velocity, for that reason. It's started to bug me really bad as in my latest employment I am expected to commit things throughout the day, but my way of working just doesn't align with that it seems. I frequently switch context between features or even projects (unrelated to one another by Git), and when someone looks at me waiting for an answer why it takes half a day to create 5 commits I look back at them with the same puzzled look they give me. Neither of us is satisfied. I spend most of the development time _designing_ a feature, then I implement it and occasionally it proves to be a dead-end so everything needs to be scrapped or stashed "for parts", rinse, repeat. At the end of the road developing a feature I often end up with a bunch of unrelated changes -- especially if it's a neglected code base, which isn't out of ordinary in my place of work unfortunately. The unrelated changes must be dealt with, so I am sitting there with diff hunks trying to decide which ones to include, occasionally resorting to hunk _editing_ even. There's a lot of stashing, too. Rebasing is the least of my problems, incidentally (someone said rebasing is hard on Git users), because I know what it is supposed to do (for me), so I deal with it head on and just reduce the whole thing to a series of simpler merge conflict resolution problems.

But even with all the Git tooling under my belt, I seem to have all but concluded that Git's simplicity is its biggest strength but also not a small weakness. I wish I didn't have to account for the fact that Git stores snapshots (trees), after all -- _not_ patch-files it shows or differences between the former. Rebasing creates copies or near-copies and it's impossible to isolate features from the timeline their development intertwines with. Changes in Git aren't commutative, so when my human brain naively things I could "pick" features A, B, and C for my next release, ideally with bugfixes D, E and F too, Git just wants me a single commit, except that the features and/or bugfixes may not all neatly lie along a single shared ancestral stem, so either merging is non-trivial (divergence of content compounded with time) or I solve it by assembling the tree _manually_ and using `git commit-tree` to just not have to deal with the more esoteric merge strategies. All these things _do_ tell me there is something "beyond Git" but it's just intuition, so maybe I am just stupid (or too stupid for Git)?

I started looking at [Pijul](https://pijul.org/) a while ago, but I feel like a weirdo who found a weird thing noone is ever going to adopt because it's well, weird. I thought relying on a "theory of patches" was more aligned with how I thought a VCS may represent a software project in time, but I also haven't gotten far with Pijul yet. It's just that somewhere between Git and Pijul, somewhere there is my desired to find a better VCS [than Git], and I suspect I am not the only one -- hence the point of the article, I guess.

> Proprietary git wrapper with pay-to-play "enterprise" gating

Oh boy. Thanks for the nightmares.

Good luck with that, I would still be using subversion if given the choice.

I refuse to use anything other than git for versioning.

I really, genuinely, do not want a replacement for git developed by a company that raised money to build it, since it will inevitably be a walled garden of one kind or another that enshittifies as it tries to make the money back. Git is fine and there is one thing no VC funded effort can get: freedom from the vampires.

Like all I see here is "We want to build a fence around git and then charge you to go through it." I mean this as kindly as I can mean it: no thank you.

"We are going to spend $17M and have nothing to show for it"

No. Just no.

Leave Git alone.

I continue to be amazed at American capital allocation. $17M for an idea to improve Git? For a fraction of that money Ukrainian housewives build anti-drone air defence systems in their garage that protect their country. For that kind of money you could build an apartment block to ease the housing shortage. You could invest in electricity resilience and build mini nuclear power plants or a small wind farm. Soviet capital allocation: while they were pouring money into their space program and building the "biggest baddest military helicopters" there wasn't enough bread in grocery stores.

Bros wanted to work on dev tools. They sold it to VCs as "AI tools" to get easy money. Well played!

> Today, with Git, we're all teaching swarms of agents to use a tool built for sending patches over mailing lists. That's far from what is needed today.

Today, with English, we're all teaching swarms of agents to use a language built from scraps of Norman French and Anglo-Saxon Old English. That's far from what is needed today.

I feel like I really need to learn how to raise money. For $17M, one could probably build a vacuum robot prototype that’ll also clean up all of the kids toys and sort LEGO bricks by colour and size. Parents worldwide would love it.

But instead, we get a replacement for Git. And I didn’t even bother to click the link because I’m fine with how Git works. On the list of pain points in my life, “what comes after Git” has roughly the same priority as “try out a more exciting shower gel”. But did you ever step on a LEGO brick while walking to the bathroom at night? That pain is immediately obvious.

Why is nobody solving actual problems anymore?

TL;DR we decided git needs more "ai" and we got money thrown at us!

Mmmh. git is perfect as it is. It does one thing and does it really well: version control. Exact bits that go in come out. And it reconciles different versions and handles transferring them to remotes.

The need for exactly this is not ever going away, and its ubiquity proves that Linus nailed something that is truly fundamental.

This is like saying we need a new alphabet because of AI. That is VC hype, even if it comes from a Github founder.