SCCS is archaic, but VSS is much /worse/. It famously loses data, for a start (hence "Visual Source Unsafe"), and is fiendishly complicated despite being less powerful than CVS. The problem apparently is that all the important Microsoft projects did not use VSS, so there was no-one competent eating the dogfood to complain about the taste. As with most really awful Microsoft products it was bought from a 3rd party to fill a perceived gap in the product line, rather than being developed in-house by smart people who understood version control.
Inadvertently Microsoft actually created a scenario in which Windows developers were less likely to even have source control, because they might try VSS figuring it's the "obvious" choice to go with their other Microsoft tools, and after losing a week's work in one click they give up altogether.
Posted Apr 4, 2010 20:26 UTC (Sun) by nix (subscriber, #2304)
[Link]
OK, colour me (un)impressed. Worse than SCCS. Worse, it sounds, than
*nothing*.
A proposed Subversion vision and roadmap
Posted Apr 5, 2010 13:43 UTC (Mon) by sorpigal (subscriber, #36106)
[Link]
This exact scenario happened to me, including the week of code and swearing off VSS forever. That was two years ago and every time since then when I've agitated for version control management has taken the "But we have VSS" viewpoint. Try explaining that not all version control systems are created equal to non-programmers, try explaining that the Microsoft product is not good enough...
A proposed Subversion vision and roadmap
Posted Apr 6, 2010 8:07 UTC (Tue) by BlueLightning (subscriber, #38978)
[Link]
Surely "even Microsoft themselves don't use it" would be a compelling enough argument?