3 ms·
Often, people's intuition is wrong on very important ways, and something that works like they expect is sure to create footguns or just blow up by itself. But
by marcosdumay 3y ago
Often, people's intuition is wrong on very important ways, and something that works like they expect is sure to create footguns or just blow up by itself.
But I'm not sure git is a case of this. The DVCS that were created following people's intuitions were known to be slow and internally complex, but I have never heard about them failing. (And the slowness is obviously of a kind that can be optimized away.)
We just stuck with the worst UI ever devised in public for a VCS because of network effects.
- chihuahua 3y agoI totally agree with it being "the worst UI ever devised". It's fine to use commits with parent pointers and branches as pointers to commits and all the other stuff internally. But there should be a UI wrapped around that that maps to operations that make sense for the purpose of working on a software project. Not this: git merge [-n] [--stat] [--no-commit] [--squash] [--[no-]edit] [--no-verify] [-s <strategy>] [-X <strategy-option>] [-S[<keyid>]] [--[no-]allow-unrelated-histories] [--[no-]rerere-autoupdate] [-m <msg>] [-F <file>] [--into-name <branch>] [<commit>… ]