More Reasons to Avoid SourceSafe
I’m helping out with a project I used to work on, one in an organization that uses SourceSafe to manage its source code. Fortunately, this time, I don’t have to deal with SourceSafe this time. All I have to do is to submit my diffs against a baseline, and someone else will have to deal with merging them into the repository.
On a more recent project, we’ve been using git. There’s no comparison. It’s pretty cool how git effortlessly handles situations that SourceSafe can’t even fathom. (Another good alternative is svn, but using svnmerge on all branches.)
Over 2 years ago, I posted a list of reasons to abandon SourceSafe. Now, since I’m hacking with Microsoft Visual Studio again on this project, I happened to run across another web page listing even more reasons why you should abandon SourceSafe as quickly as possible.
Chuckle, chuckle. Thank God that I don’t need to touch it.
-TimK
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
Comments
No comments yet.
Leave a comment