This article has a few points. First of all, the author wants backup, switching machines, and collaboration all integrated into VC. This is a worthwile goal,

This article has a few points. First of all, the author wants backup, switching machines, and collaboration all integrated into VC. This is a worthwile goal, and i can see that shoehorning git et al into those rules can feel... clunky. I think there is room for improvement there. The author comes off a little greedy, when he wants to (a) be able to instantaneously create a new workspace while (b) being able to manage huge code bases. Oh, and everything should work even on his chromebook - as long as he has one computer that can do the work, all his other computers should offload the work to the one capable of doing it. Transparently of course. This sounds great and all... but i would not want to implement it :-)