[geezerjay]

> Its user interface is a landfill fire.

Are we talking about the same Git? Its command line interface is quite straight forward and very simple to use to perform the usual everyday tasks.

Can you actually point out a single example of what you perceive as a "landfill fire"?

[shaftway]

Can you give a succinct definition of what `git add` and `git checkout` do without relying on documentation?

[geezerjay]

Is it that hard to understand that `git add` adds files to the list of files tracked by the repository (which is updated when changes are committed to it) and `git checkout` checks out a version that has been previously committed?

I mean, that's pretty much how all version control systems operate. Is it that hard to wrap anyone's head around the basic functionality that is common to any version control system in use?

[throwanem]

No, it's not that hard to understand. It's also not how Git actually works. You're ignoring, or perhaps forgetting, the concepts of the index ("staging area"), and the many and various things which both these commands actually do, and the fashions in which these sorts of "oh, it's simple, really!" elisions betray those not yet experienced enough to recognize them for the overextended abstractions they are.

[throwanem]

I'm talking about the same Git as the article author is. If you have a different Git in mind, please point me to it! Perhaps I would prefer to use that one instead.

[geezerjay]

I see you failed yet again to provide any example to substantiate your baseless claims.

[throwanem]

The article's full of them! That wheel doesn't need reinventing.

I get that you like Git's UI, or at least don't mind it. That's fine. Others feel differently. That's fine too.

[cellularmitosis]

This is the most obscure command mentioned in the article:

    git rev-parse --abbrev-ref HEAD