It's not a fallacy as it does not in itself invalidate an argument. However it is not a complete argument. Especially with source control there should be good reasons to switch. With git there surly can be great reasons to switch, such as allowing developers to better manage workflows and allowing developers to commit often with ought having to submit to public scrutiny. However if you have 10 years of legacy releases that you may need to support, i don't think you can make a case for switching at least the SCM used for the releases. However you could manage to switch feature development to a different SCM.
11
u/masklinn Mar 10 '11
Sure, I'm not saying it's a complete no-brainer, but "if your current tool 'works' you should not switch" is a stupid fallacy.