Live data from Hacker News

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

blog.gitbutler.com

331–340 of 785 posts

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

#331

Earlier quoted context omitted.

> ... and sort LEGO bricks by colour You never sort by color, ever! You sort by form, and then throw every color of that specific form in one bin. If you throw every red brick in the same bin, you'll never find a specific formed red brick because to many red bricks. But if you first search by form and then by color, you are much faster.

As someone who tried to sort many lego sets lately, I do like this. The problem lies that modern lego has so many unique forms that it feels like you'll have many bins with one or two pieces in.

That's why you buy different sized bins, and then you can even combine some forms into one bin (but be careful not to combine similiar forms, this counters the goal).

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

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

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

#335
post #164

Earlier quoted context omitted.

that's a company built on top of Jujutsu, not jj itself

If I remember correctly, jj is one guy who works at Google. Which presents a separate worry, which is that one day, when jj gets popular enough, Google will consume it, make it shit, change the name of it every six months and then shut it down.

That hasn't really been the case for a while imo: Martin works at Google and is paid to work on jj (there are also other Google employees who contribute, not sure whether they're paid to). jj is in use (wide use? No idea) alongside Google's internal tool (piper) with which it can interact (and with which it has some features in common) because jj has a pluggable backend architecture.

While I hate to engage in speculation, tell spooky stories, or screech at people about the evil CLA you have to sign in order to contribute, my personal opinion is that if Google were ever to start throwing their weight around, the project would be forked in short order and development would continue as normal – it has momentum, plenty of non-Google contributors, and a community. It's also not a product per se, though as we're about to find out, you can certainly build products on top of it – that probably makes it less likely for its current home to suddenly become proprietorial about it.

(hi Andy!)

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

#336

Earlier quoted context omitted.

Gitbutler is backed by git. Gitbutler is essentially just ui for git which also allows you to have multiple branches. It isn't meant to replace git.

What does that even mean? Multiple branches is a git feature.

‘Embrace, extend, extinguish.’

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

#337

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. GitB…

So they decided to start "embrace, extend, and extinguish" directly with with "extinguish".

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

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

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

#340

Earlier quoted context omitted.

If I remember correctly, jj is one guy who works at Google. Which presents a separate worry, which is that one day, when jj gets popular enough, Google will consume it, make it shit, change the name of it every six months and then shut it down.

That hasn't really been the case for a while imo: Martin works at Google and is paid to work on jj (there are also other Google employees who contribute, not sure whether they're paid to). jj is in use (wide use? No idea) alongside Google's internal tool (piper) with which it can interact (and with which it has some features in common) because jj has a pluggable backend architecture. While I hate to engage in specula…

Good points. I had a horrible vision of a git -> GitHub -> Microsoft -> GitHub-on-Azure style pipeline but yeah, I think there's enough good people involved around jj that your vision is probably more likely. Also, hi Steph!
Post reply on HN