loading...

Discussion on: Git - Command line vs GUIs

Collapse
gonedark profile image
Jason McCreary Author

We might be closer than you think. Your statement of:

To understand git you should not use a GUI

Is in perfect agreement with my points.

Collapse
phillijw profile image
Joe Phillips

I would argue the exact opposite. The commands are not the important part of git -- the understanding of how the tree is shaped and how the child/parent relationship works is. That is a lot easier understood visually than textually.

If you are simply memorizing commands, you're not utilizing git to its potential.

Thread Thread
gonedark profile image
Jason McCreary Author

You're extrapolating too far. The commands are indeed not the important part of Git, understanding how Git works is important. We're in perfect agreement.

This article suggests a GUI may abstract this and deprive someone just starting out with Git the chance to learn as much as they may from the command line.

There may be some availability bias here since you're already comfortable from Git. I also have a firm grasp on Git and use a GUI for some of the more visual aspects of Git (tree differences, code review, etc). Nothing wrong with that.

In the end, if the only way you know Git is by pressing some buttons in a GUI, then you don't really know Git. I encourage those to try and use the command line to drive their understanding of Git.

Thread Thread
phillijw profile image
Joe Phillips

I would be curious to see some evidence that implies people who use the command line understand git more than those who use GUI. I think this a bad assumption.