Agreed. This article is stupid because it extrapolates from a few cases he's seen personally (and it was his coworkers messing up; I'm sure he's such a good developer that he's never made a mistake attributable to the command line tool, like making a typo).

And as long as we're being totally unscientific about the whole thing, the most common mistake I've seen when using a version control system has come from people checking in unintentional modifications using the command line tool because it is easy to miss. In a GUI, you can better see what is being committed, and a simple checkbox lets you skip it, while double clicking gives you a diff that makes it so much easier to review every change before you commmit.

There's a comment in the article that also recommends Tower. I've personally been looking for a Tortoise replacement. What makes Tower so good?

It's pretty much 1:1 to git command line.

Most times when someone on my team screws up a commit, it's because they botched the command line (the inverse of this article's claims). Fix it in Tower in a few minutes in a visually simple way that helps them understand what's going on.

It also makes submodule usage do what you think it should do.