News for hackers. Stuff that matters.
Re:We've raised $17M to build what comes after Git by IshKebab on Friday April 10, 2026 @03:47AM (#47714892)
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.
Re:We've raised $17M to build what comes after Git by a-french-anon on Friday April 10, 2026 @04:04AM (#47715013)
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).
Re:We've raised $17M to build what comes after Git by k4rli on Friday April 10, 2026 @04:25AM (#47715175)
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.

Re:We've raised $17M to build what comes after Git by dare944 on Friday April 10, 2026 @06:41AM (#47716066)
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 by weedhopper on Friday April 10, 2026 @05:53AM (#47715737)
Rust! it’s written in rust and not javascript!!!!
Re:We've raised $17M to build what comes after Git by theappsecguy on Friday April 10, 2026 @08:42AM (#47717256)
I would urge you to take a look at the founding team here, I doubt that they vibe coded this tool.
Re:We've raised $17M to build what comes after Git by hk__2 on Friday April 10, 2026 @04:25AM (#47715176)
> 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.

You can define your own merge strategy that uses a custom executable to fix conflicts.

https://stackoverflow.com/a/24965574/735926

Re:We've raised $17M to build what comes after Git by DonThomasitos on Friday April 10, 2026 @04:41AM (#47715268)
„Claude, merge these branches and resolve conflicts. Ask me if unclear.“

16M$ VC money saved.

Re:We've raised $17M to build what comes after Git by IshKebab on Friday April 10, 2026 @08:13AM (#47716910)
I'm sure that will go well for my formal model in a language that about 100 people use...
Re:We've raised $17M to build what comes after Git by _fizz_buzz_ on Friday April 10, 2026 @08:34AM (#47717165)
If only 100 people in the world are using this language, who are you even merging code with, lol.
Re:We've raised $17M to build what comes after Git by IshKebab on Friday April 10, 2026 @10:12AM (#47718471)
Some of the other people?
Re:We've raised $17M to build what comes after Git by user34283 on Friday April 10, 2026 @05:00AM (#47715387)
So far I have not let AI work with git, because I preferred handling version control myself.

Does it work well for resolving merge conflicts in your experience?

Re:We've raised $17M to build what comes after Git by speedgoose on Friday April 10, 2026 @06:28AM (#47715990)
Not the person you responded too, but in my experience the answer is a big yes.
Re:We've raised $17M to build what comes after Git by hrimfaxi on Friday April 10, 2026 @08:51AM (#47717370)
In my experience, yes. It has done a great job of choosing which changes should be integrated based on context in the repo, too.
Re:We've raised $17M to build what comes after Git by skydhash on Friday April 10, 2026 @08:23AM (#47717026)
> 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).

Re:We've raised $17M to build what comes after Git by IshKebab on Friday April 10, 2026 @10:26AM (#47718676)
> 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

Re:We've raised $17M to build what comes after Git by 1718627440 on Friday April 10, 2026 @02:33PM (#47721929)
> where Git's *default* merge algorithm gives you horrible diffs

You are saying it yourself.

Re:We've raised $17M to build what comes after Git by IshKebab on Friday April 10, 2026 @05:42PM (#47724006)
Saying what? Defaults matter. The fact that other people are doing their best to improve Git's mediocre defaults doesn't excuse it.

I doubt you would defend any of Windows' poor defaults because there are tools to fix them.