I don't know if you can draw that drastic of a conclusion from his post without some other knowledge of his particular situation. For some people Git offers very little advantage over SVN, a small team with a single desktop or embedded produce is not going to see the same advantages of a DCVS system that a massive web team does that is seeing daily releases. As such a developer with their use case may feel that the effort to learn it for their situation was not worth the effort.
"For some people Git offers very little advantage over SVN, a small team with a single desktop or embedded produce is not going to see the same advantages of a DCVS system"
I disagree, actually. Small, informal teams can use pretty much whatever they want with little penalty, and may actually benefit from having distributed repositories. Larger teams rarely need distributed version control (there's almost always a canonical central repository), and are also the ones most penalized by the complexity of git.
Git is a complex, confusing beast with a high potential for mistakes. There are some nice things about it, but (from personal experience) it also tends to create as many new problems as it solves. These problems are amplified on large teams.