5 ms·

In the Windows world SCM was not generally available until SVN was released as a File Explorer extension. This was sometime in the 2000s. Git took several years

• GordonS 5y ago
  IIRC, Microsoft's TFS (Team Foundation Server) also came on the scene in the early 2000's. I first used SVN around that time, before TFS became the standard at Microsoft shops.
  • andrewaylett 5y ago
    My first employer out of university kept their code in Visual Source Safe, Microsoft's first attempt at a VCS. It was really, really bad. My second employer used CVS. Tags were fun back then -- each file was versioned separately so committing multiple files while a tag was in progress might result in only some of your changes making it into the tag. My big innovation there was to add a validation step to our build machine to ensure that the tag matched the state of the branch once the tag had finished, and add the tag to the build version number. Presto: we can actually see which code was built into that day's full build :).
• kryptiskt 5y ago
  There were plenty of proprietary source control systems around. At my first job in 1998, we used Visual Sourcesafe, later switching to Perforce. At another job I had the misfortune to get to know Rational ClearCase.
  • kevstev 5y ago
    I am absolutely stunned that people think that source control only came around recently in this thread. CVS came out in 1990, RCS... 1982, SCCS... 1972. Visual Source Safe was commonplace in the 1990s, as terrible as it was. There may have been small teams that didn't use SC in the 1990s, but this has absolutely been a basic best practice for decades.
• atrn 5y ago
  There were others far before Windows. In the 1980s I used Polytron version control system and the MKS port of RCS on MS-DOS.