I suspect there might have been a touch of sarcasm in that VSS remark
Re:Branchless development
by radicalbyte on Sunday July 19, 2015 @11:22AM
(#9911448)
Yes, I was being sarcastic. Sorry for confusing you koonsolo.
Visual Source Safe is an absolute pig, unless you're already using it and can't switch then I strongly advise getting as far away as possible.
Team Foundation Server - the replacement - has historically been just as poor. It does however have the advantage of including some extremely powerful software lifecycle management features.
Recent developments - such as the Git-based Team Foundation Online - are really rather good, especially if you need more advanced features and like giving Microsoft money ;)
I agree with the VSS-hate, of course, but it's unfair to say that TFS is just as bad. TFS is annoyingly difficult to administer, but it's a zillion times more robust than VSS, and compares favorably to Subversion or Perforce (and has excellent Visual Studio integration).
Git totally kills it, of course, but as traditional old-school VCS goes, it's not bad at all.
I introduced Subversion. No more corrupt files (shiver), it just kept on running. And you could actually work on any file. If you divide your work properly, you can work in the same file without working in the same code. And if the small chance of changing the same line occurs, the merge wasn't that complex to fix.
We never looked back, and therefore I am completely disgusted that someone actually suggests using such an unstable, non-efficient tool.