[1] I haven't used TortoiseGit, but I do imagine that having file browser menu items for files that are maintained by git could be useful from time-to-time, but I would still be using the cli most of the time.
[2] Directed Acyclic Graph
[1] I haven't used TortoiseGit, but I do imagine that having file browser menu items for files that are maintained by git could be useful from time-to-time, but I would still be using the cli most of the time.
[2] Directed Acyclic Graph
The only one that draws serious usability complaints all the time is git.
* Unreasonable ideas about the idea that commits/history can be rewritten, so therefore "nothing is safe."
* Arguments over how some git commands are similarly named to svn commands, yet don't do the same thing. The svn way is the 'right' way, and git is 'doing it wrong,' but really it's just an argument about familiarity (sharing many traits with arguments over Mac vs. Windows keyboard shortcuts, for example).
* Complaining about a recoverable error because they don't know about the reflog.
* etc.
I'm sure there are legitimate complaints, but most of the complaints that I see are around things like that.
git won for various reasons, but the UI complaints certainly aren't because people don't understand DAGs.
Yes, but how many weeks and months did you spend learning all the quirks? http://git-man-page-generator.lokaltog.net
that people have trouble wrapping their minds around.
If you create a product and just tell people "sorry, you're not smart enough to understand it," was it a good idea?