The interesting thing about this otherwise misguided post is that there are now people who started out on Git who are struggling to adapt the older, server-base

The interesting thing about this otherwise misguided post is that there are now people who started out on Git who are struggling to adapt the older, server-based workflow. It's really not about Git vs. SVN. It's about distributed vs. centralized VCS. I think programmers are realizing that there's truly an advantage to the DVCS approach but the discussion quickly becomes emotional and irrational. The net result of sucks-vs-rocks discussions are just damage to the cause of newer technologies. I've used RCSs (RCS,PVCS,VSS(^%$#^$%),MKSSI,CVS,SVN) for so long that the latest versions of SVN, which support branching (though not so well), seem very comfortable and luxurious. The Eclipse plugins like Subclipse or Subversion for updating and merging files make CVS/SVN almost is a pleasure to use. However, there are workflows and tasks that DVCS systems support much more naturally and it's that aspect that should be discussed.