Sure. The problem is not "distributed version control", some problems are:

- I'm on a train with no internet, finished working on a thing and want to start working on another thing and don't want to mix them up.

- I want to make a branch and don't want to wait for eons while everything gets copied on the server.

- Oops there's a problem with the server now no one can perform any work.

Yes, SVN might simple commands, but its internals are messed up. Git's UI sucks, but just learn about blobs, trees, commits, branches (pointers to commits), and you basically understand how Git works.

SVN feels like working in someone else's kitchen while several other people are trying to cook in it, too. It's hell. I prefer that we each have our own kitchen and bring our dishes to the table when they're ready.

I've also repeatedly found git a suitable (if not great—if they'd put all their effort behind libgit2 and make that the official implementation, that'd help a ton) tool to form the foundation of larger systems. It's a damn fine toolbox for attacking certain problems. SVN wouldn't have been much help in any of those situations.

And I thought I use git in a decentralized fashion all the time … at least I don't need to connect to any other machine when committing, switching branches, merging, rebasing, etc. And my colleagues can do the same without any network connection at the same time.

Also, while it has the biggest brand recognition, not everyone is using GitHub for all their repositories, are they?