← Back to context

Comment by tmountain

2 days ago

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.

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.

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.

    • I would urge you to take a look at the founding team here, I doubt that they vibe coded this tool.

    • 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.

  • Well, yeah, but Git is basically UNIX/POSIX or JPEG. Good enough to always win against better like Plan 9 or JPEG XL (though I think this one may win in the long term).

  • > especially for dealing with rebase/merge conflicts where I would say Git is mediocre.

    It seems like everyone that hold this opinion want Git to be some magical tool that will guess their intent and automatically resolve the conflict. The only solutions other than surfacing the conflict are locking (transactions) or using some consensus algorithm (maybe powered by logical clocks). The first sucks and no one has been able to design the second (code is an end result, not the process of solving a problem).

    • > It seems like everyone that hold this opinion want Git to be some magical tool that will guess their intent and automatically resolve the conflict.

      Absolutely not. There are plenty of fairly trivial solutions where Git's default merge algorithm gives you horrible diffs. Even for cases as simple as adding a function to a file it will get confused and put closing brackets in different parts of the diff. Nobody is asking for perfection but if you think it can't be improved you lack imagination.

      There are a number of projects to improve this like Mergiraf. Someone looked at fixing the "sliders" problem 10 years ago but sadly it didn't seem to go anywhere, probably because there are too many core Git developers who have the same attitude as you.

      https://github.com/mhagger/diff-slider-tools

      2 replies →

> but with people throwing money behind it, there’s a plan to extract value from the user base from day one.

They'll start injecting ads in your commit messages, forcing you to subscribe to a premium plan.