4 ms·
That's an interesting stance. There are things I can do in http://git-cola.github.com/ http://git-cola.github.com/ that I simply can't do on the command-line.
by davvid 14y ago
That's an interesting stance.
There are things I can do in http://git-cola.github.com/ http://git-cola.github.com/ that I simply can't do on the command-line. That's why I use a GUI.
To be fair, I wrote it, so I know exactly what commands it runs. I do think I've done a decent job of making it very clear what's going on under the hood, though. I even have a mode where the tool prints every git command it runs.
In general, though, I agree that folks should have an understanding of the underlying concepts. That way the GUI becomes a supplementary tool (rather than a crutch). This advice is not limited to just GUIs, though.
- zem 14y agoagreed, git-cola is way more usable than the git command line for breaking your uncommitted changes into a series of partial commits. that's the one time i will absolutely use a gui tool as being the best tool for the job.