> This is the biggest red flag about git's CLI. I shouldn't need to know the implementation to use the UI. This speaks to a fundamental misunderstanding of the

> This is the biggest red flag about git's CLI. I shouldn't need to know the implementation to use the UI. This speaks to a fundamental misunderstanding of the nature of Git. You need to know the model of anything to be able to use it properly- you've mixed up Git's model with its "implementation" (probably because Git's model is so lightweight and exposes a lot of its fundamental workings, [as is right for proper usability][1]). This is like saying you shouldn't have to know what files and folders are to open a document in Word, Yes, you should. [1]: http://en.wikipedia.org/wiki/Seven_stages_of_action#Usage_as_Design_Aids http://en.wikipedia.org/wiki/Seven_stages_of_action#Usage_as...