it's a revision control system for pete's sake. it should track revisions in your code and let you get back to work.
The fact is that proper version control is a hard problem. Tracking your work quickly and simply without forcing you to conform to a workflow prescribed by the VCS tool itself is a non-trivial problem (unless of course your work is itself trivial). Git solves this problem elegantly and efficiently and the amount of information popping up recently are from users who are thrilled that a tool finally exists that does not limit how they do their work and who want to share that with others so they can work better too.
I am driven to do all the Git related stuff that I do because I love the tool and it is so much better than what I had ever used before, not because it's frustrating to me or I feel it's hard to use.
But there are things about git that are non-obvious, and tricky if you've been accustomed to cvs, svn, or even hg.
It's sort of like learning OOP after years of BASIC. Once you get going, you may wonder what was so hard about it, but getting a proper mindset can be difficult.
Once I get all the same material covered, I'll probably start redirecting this site to the new one. I'm actually just finishing up a print book with Apress on Git that is CC-3.0 licensed, so I'll be putting a site with the contents of that book online soon too (then I'll have some free time to finish up the learn.github.com site).
The approach he uses is very similar (a little bit more detailed) to this tutorial ("Understanding Git"): http://news.ycombinator.com/item?id=531517
I can't really go at my own pace, or skim, like I can with a web page. I can't cut and paste.
I can see why they appeal, TV vs. book etc. etc. Less perceived effort.
