Live data from Hacker News

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

blog.gitbutler.com

321–330 of 785 posts

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

#321

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.

Just keep those in a single bin

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

#322
post #34

Earlier quoted context omitted.

I like git, it works perfectly fine on my command line. I do wonder, though, if it would have been designed differently if the whole “code forge” sort of application (or whatever GitHub and the like are called) was envisioned at the time. Pull requests aren’t even a concept in git proper, right? It seems like a kind of important type of tool. Even though git is awesome, we don’t need a monoculture.

À pull request is just you requesting someone to pull from you in git proper. So the maintainer adds you as a remote and pulls from you.

There’s really nothing resembling a “pull request” that’s used by 99.999% of git users. We have merge requests. But we call them pull requests for some dumb reason.

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

#323

Earlier quoted context omitted.

On one hand that’s true. On the other, the “one guy” there is, like, the guy who does impressive projects “just as a hobby.”

Yeah, it's really burying the lede to call Linus Torvalds "one guy with a chip on his shoulder". "Why fund $17M towards development of an operating system, when Linux was made by one guy with a chip on his shoulder?"

While he's technically excellent (or so it seems on the outside) he's still just, like, a guy

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

#324
post #140

Earlier quoted context omitted.

Guessing you aren’t working with hundreds of collaborators in a distributed offline system. Which is what git was for and why svn wasn’t enough for that type of use case.

u guessed right. im one of the world's few solo software developers left (behind).

Keep on keeping on brother.

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

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

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

#326
post #295

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 com…

Just a reminder that even if you managed to amend those commits and force-push, the commits would still exist and will be addressable given the hash is known.

Can't they be purged if they are dangling and the housekeeping is ran?

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

#327
post #119

Earlier quoted context omitted.

Yes, it’s fantastic. I have a post-tool-use hook for Claude Code to snapshot the repository for every edit. It’s like the built in file history feature but native in my VCS and works for my edits too. Don’t want to froth too much but JJ is my favourite piece of software in a while, and the fact that it’s not VC-funded is a major plus point.

Its VC funded https://www.sec.gov/Archives/edgar/data/2076429/000207642925...

Jujutsu is not "VC funded". But some of the developers, including me, work at East River Source Control (I worked on Jujutsu before that, too). The majority of the code in the project doesn't come from us -- or Google, for that matter. We don't allow people to approve patches when the author is from the same company, anyway.

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

#328

I refuse to use anything other than git for versioning.

Standard is better than better. For all of its flaws, I’ll take Git any day over any (better) alternative, because the value is in the absence of fragmentation. If a repo doesn’t use Git, I’m out.

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

#329
post #204

Earlier quoted context omitted.

Git is fine. I would like something better than fine though, especially for dealing with rebase/merge conflicts where I would say Git is mediocre.

What about a vibecoded replacement with emojis and javascript? Surely $trillion "ai" thing can generate a better solution than one Finnish guy 20 years ago.

Lol. Unfortunately VCs and ever-so-ernest founders are impervious to irony. Best to just let them get their grift on and just be happy it isn't your money they're boondoggling.

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

#330
post #313

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.

counterpoint (don't take this to seriously): there are to many types of bricks to sort by form. unless you have an inventory the size of a brick factory you can only sort by category or by size. otherwise, sorting by color makes your collection aesthetically pleasing, and when you build, you usually want to use specific colors only to make your model look good.

There are less different forms than any normal brick enjoyer has bricks of a specific color. Therefore the lookup is faster ;)
Post reply on HN