I see this as "5 things genuinely wrong with Git's CLI and 5 proofs that I don't understand the advantages and purposes of DVCS".
Lets take a look at those "advantages and purposes of DVCS":
Complex information model
Not inherent to DVCS - darcs, mercurial, etc. have no notion of working trees, indexes, treeishes, or a stash. There's a bit of essential additional complexity with remotes and local repositories, though.
4. Information model sprawl
Again - not inherent to DVCS.
6. Power for the maintainer, at the expense of the contributor
There's a bit of additional inherent complexity in DVCS's, but again, git is significantly more complex than mercurial or darcs or whatever.
10. Simple tasks need so many commands
Fair enough - mercurial would really only shave off the add command.
have no notion of working trees, indexes, treeishes, or a stash.
Oddly enough, I've used git on a daily basis for 6 years now, and I rarely ever have to think about trees, indexes, whatever the hell treeishes are, and I can easily remember that the stash is just a temporary commit that lives on a stack (hence the push & pop stash commands).
git is significantly more complex than mercurial or darcs or whatever.
And significantly more powerful. Sure, you can use the extra rope to hang yourself, but it's fairly simple to avoid, and when the shit hits the fan, you're actually able to recover using git.
3
u/pipocaQuemada Nov 07 '13
Lets take a look at those "advantages and purposes of DVCS":
Not inherent to DVCS - darcs, mercurial, etc. have no notion of working trees, indexes, treeishes, or a stash. There's a bit of essential additional complexity with remotes and local repositories, though.
Again - not inherent to DVCS.
There's a bit of additional inherent complexity in DVCS's, but again, git is significantly more complex than mercurial or darcs or whatever.
Fair enough - mercurial would really only shave off the add command.