I'd prefer to phrase it as "this different interface also supports your workflow". Whether the different interface is better or not is completely independent f

I'd prefer to phrase it as "this different interface also supports your workflow". Whether the different interface is better or not is completely independent from when it was developed in relation to an existing interface. For example, I find debit cards a much preferable interface to the "pay for things from your bank account" workflow over writing checks, and checks were developed much earlier. :) An interface is only as good as the power it gives you. Recall that power is work/time, so you can increase power by increasing work or decreasing time [1]. It's better if it's easier or faster to use and you can overcome the transition/initial learning costs. I'd guess that the vast majority of typical users of git have to pull up the git man pages (or stackoverflow) to do most of the actions shown in this article, hinting that such an interface may both save time and increase work (users often just not do stuff that they have to research to accomplish). [1]: Ok, I might be stretching the physics analogy a bit. :P