Git is as easy to use as scp or rsync from the commandline for most common tasks. So is Tarsnap.
The Tarsnap -> Patio11's Idea is being approximated as equivalent to Git -> GitHub.
So, in this context, the people I've dealt with that would want Patio11's Idea of Tarsnap are people who don't want to take the effort to understand what they are dealing with.
GitHub has a larger audience that has nothing to do with development. Social features, simplifying things for non-developers, etc. but I do not feel that portion of the 'product' is relevant in this context.
The people I know IRL that prefer a GitHub-type interface over doing things with Git via the command line are the type that need me to fix the issues they run into for them. The fact I'm basically git support for other IT folk leads me to that conclusion.
And frankly, I'm not a Git guru. I'm a very, very average software developer who acts as the sysadmin for Dev at $DAY_JOB.
I fully believe other people have different experiences but I've implemented Git workflows at 2 companies now and I've seen a consistent pattern.
Please do understand, I'm not saying they should or need to learn Git. It is better they focus on the domain expertise they bring to the table [e.g. Web Design, Email Design, Data Science]. I'm just saying it is a different audience than Tarsnap's current one.
I'm one of them. For me it's because I made some token efforts before to understand it, and it seemed far more complicated than source control should be. I have very simple needs, and correspondingly don't really have a desire to learn non simple tools.
