Sure. Few clients (any?) support rebasing or squashed merge commits. So if you work with people who like a simple single-commit-per-feature workflow on the master branch, you're left learning the CLI. Also, "shared lingo": cryptic error messages have been stated elsewhere on this post, and there's no reliable way to tell people how to resolve them (if it's even possible in the GUI they're using).
And stop being an ass by assuming I'm being an ass, please.
Does one missing feature really make them anaemic?
I understand the git system just fine, I've worked with many other developers who use a disparate set of git tools and I've seen no such problem. I rarely touch the command line and it's just amazing - it's like I have this brain that can understand a system without using the same exact tool that you use to work with it.
Really, I just love the elitist remarks from people who love the command line.