You could have replaced the topics of svn and git with C++ vs python or stored procedures vs parameterized queries and it would have been practically identical apart from people would have told him to sod off and grow up instead of changing their process.
That's actually the only positive take away from this article, it is actually really easy to change version control system if you want to.
I must admit I'd love to see the post he'd make after being forced to use MS VSS :)
s/older/unfamiliar/
I absolutely agree with that substitution. You can (and I certainly do) see the exact sort of thing going on in the reverse direction with various technologies. I'm guilty of it myself. That's why I find it interesting.
What's better, a development team full of developers who are flexible enough to use a crappy technology, or inflexible enough to move the product to a superior technology? It depends on moving costs and the difference between technologies, but in some cases I think that inflexibility is better.
"A good developer can work with crappy tools and make great things."
So what exactly is your point here?