5 ms·
I’d take a new git with just the UX fixed. If the underlying implementation of a new VCS is also better, that’s great, but my main problem with git isn’t that i
by alkonaut 6y ago
I’d take a new git with just the UX fixed. If the underlying implementation of a new VCS is also better, that’s great, but my main problem with git isn’t that it’s not sound but that the UX is a steaming pile of legacy cruft, and it’s really more an API for version control than a polished interactive app for humans.
- ptx 6y agoThe OpenBSD developers are apparently working on something[1] like this. Another major focus seems to be privilege separation and security. [1] https://gameoftrees.org/ https://gameoftrees.org/
- pmeunier 6y ago> the UX is a steaming pile of legacy cruft This is due to the lack of a solid theory to match the intuition. The "git way" of trying to match each use case is to add a new command for each new use case. I don't think you can fix "just the UX" without fixing the underlying algorithms.
- alkonaut 6y agoAs an example of the UX issue: just making command line switches consistent (e.g. delete always being the same switch) would be a very easy fix and a UX win, and it's only compatibility holding that back.
- rkangel 6y ago> The "git way" of trying to match each use case is to add a new command for each new use case. To me, git's problem is the exact opposite - the commands are based on how the underlying technology works, not on the use case for the user. The best example is 'reset'. I understand git's internals reasonably well so I know the reason why, but it's not obvious that you need the same command to "un-add" a file, or to wind history back two commits.
- sideeffffect 6y agohave a look at https://gitless.com/ https://gitless.com/ A talk introducing the issues with git and how gitless improves upon them https://www.youtube.com/watch?v=31XZYMjg93o https://www.youtube.com/watch?v=31XZYMjg93o
- Cloudef 6y agoI think people should learn to use git rebase.