Sorry, but this is a terrible analogy. The core problem with it is that very few people can get paid more by being better at using their [D]VCS, whereas those

Sorry, but this is a terrible analogy. The core problem with it is that very few people can get paid more by being better at using their [D]VCS, whereas those more skilled with their programming language(s) of choice often do get paid more to wield that knowledge. Consequently, most people do not fully master their version control system to the same level that they do with their programming language, their text editor, etc. To be specific, there are many more C++ wizards and Vim wizards than there are Git wizards. In situations like this, I prefer a tool that lets me pick it up quickly, use it easily, and then put it back down again without having to think too much about it. You see this pattern over and over in software. It is why all OSes now have some sort of Control Panel / Settings app, even if all it does is call down to some low-level tool that modifies a registry setting, XML file, or whatever, which you could edit by hand if you wanted to. These tools exist even for geeky OSes like Linux because driving the OS is usually not the end user's goal, it is to do something productive atop that OS. [D]VCSes are at this same level of infrastructure: something to use and then get past ASAP, so you can go be productive.