title: Why is Visual SourceSafe viewed so poorly?
body: <p>I'm interviewing this week for a position at a firm where I would be the sole initial developerplus support the application I am taking over work for. Because positions like this can vary so wildly in the details, I plan to go in advocating a number of specific approaches that would make the job workable.</p>
  <p>One thing that I'm considering bringing up is an inclination to move the existing source code out of SourceSafe (where it is currently resident) into a better version control product like Perforce.</p>
  <p>I've had a number of bad experiences with SourceSafe causing massive problems like permanent file lock-out and code corruption. Alone, I'm afraid that those anecdotes sound like &quot;I want to change it because I don't like it.&quot; If I'm going to bring the subject up, I want to have a slam dunk case.</p>
  <p>So, what are the empirical reasons that SourceSafe is viewed as an inferior product?</p>
  <hr />
  <h3>See also:</h3>
  <blockquote>
  <ul>
  <li><a href="https://stackoverflow.com/questions/520926/any-real-life-visual-source-safe-horror-stories">Any Real-Life Visual Source Safe Horror Stories</a></li>
  <li><a href="https://stackoverflow.com/questions/115493/how-do-i-convince-my-team-to-drop-sourcesafe-and-move-to-svn">How do I convince my team to drop sourcesafe and move to SVN?</a></li>
  </ul>
  </blockquote>