←back to thread

94 points vincent_s | 3 comments | | HN request time: 0s | source
Show context
hakube ◴[] No.40915275[source]
why does Git need to be replaced?
replies(2): >>40917348 #>>40920741 #
1. lawn ◴[] No.40920741[source]
Because there are several issues with it?

Terrible cli user experience and having to resolve the same rebase conflict again and again for instance.

And maybe because other tools do things better?

replies(1): >>40925075 #
2. hakube ◴[] No.40925075[source]
I have been using Git for 8 years and haven't had any bad experiences with CLI. And this one and other tools that are supposed to replace Git are better in what way? The only thing that's better in this is the conflict resolution but other than that, it doesn't offer that much.
replies(1): >>40925710 #
3. lawn ◴[] No.40925710[source]
I've used Git for over 16 years and have countless of papercuts with the CLI. Of course as you grow more experienced you eventually memorize the commands you end up using despite them not having much consistency (git checkout removes files, but it also changes or creates branches for instance).

This is a major pain for people learning Git for the first time and basically everyone have run into these issues, while a more user-friendly tool would've saved so much pain and suffering. There's a reason why most people cling to a Git GUI like their life depends on it.

Being easier to learn and reason about together with better conflict resolution and rebasing are substantial improvements I'd say.