Live data from Hacker News

We've raised $17M to build what comes after Git

blog.gitbutler.com

571–580 of 785 posts

Re: We've raised $17M to build what comes after Git

#571

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.

Getting it is not the hard part. Keeping it in light of an adversarial, litigious contender is.

Re: We've raised $17M to build what comes after Git

#572

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…

Every success story and happy conversion to jj is evidence that hg should have won the DVCS war, but more importantly, that VCSes and their inherent merits and tradeoffs were always secondary to the social networks underpinning them. GitHub as a defacto monopoly really killed innovation in the VCS space, but also shifted the focus and attention elsewhere. That's why I don't think there'll be so much of a "post-git" without as much as a "post-github".

Re: We've raised $17M to build what comes after Git

#575

Earlier quoted context omitted.

I'm trying not to comment on too many of these, but this one is interestingly wrong to me, so why not indeed? GitButler came about many years ago because I have been using Git for almost the full 20 years of it being around and I thought there could be a better way to do the things it's trying to solve for us. I want version control to do more for us, easier, faster and smarter. Git is still pretty dumb. Plus, now, e…

Why is GitButler still using Git if Git is the problem? > As a _single_ example - agents can't use interactive editors, yet _so many_ of the powerful parts of Git absolutely _require_ it. Agents can't interactively rebase, meaning they can't very effectively squash, amend, reword, reorder, absorb. They can't very easily interactively add. They are middling at best when it comes to stacking branches. Git is designed t…

Git is awesome in lots of ways. As a data storage layer and as a transport protocol, it's pretty great. The porcelain was built for a different era and is slow to adapt. Originally, Git was meant to just be these primitives and everyone was supposed to write their own "porcelain" or SCM on top. We're doing that and then some - creating new standards for more metadata, real time communications, built in review, etc. If anything, we're going back to the original point of git and doing what Linus wanted other people to do in the first place - write a good SCM for their workflows on top of the foundation he started.

Re: We've raised $17M to build what comes after Git

#576
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?

Re: We've raised $17M to build what comes after Git

#577
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.

Re: We've raised $17M to build what comes after Git

#578
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.

Re: We've raised $17M to build what comes after Git

#579

- 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

Seeing all of these investments in developer tooling projects makes me wonder/skeptical of what the next chapter of development looks like when the money spigot runs dry.

I've not used this app, but I wonder how tooling like this truly competes against an open source community armed with AI. Like where is the moat here, really? I built a personal tool that does some of this with a basic Claude subscription over the course of a few weeks.

Feels like vibe-coders are the real target market for something like this, but if it takes off, would not be that hard to clone as a FOSS app.

Re: We've raised $17M to build what comes after Git

#580

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?

Unless one wishes to control the entire ecosystem rather than simply participate in it.
Post reply on HN