Microsoft Visual SourceSafe (Discontinued) vs. Yarn

The only time I could recommend Microsoft Visual SourceSafe would be for a beginner who has a small amount of code that they would like to keep track of. This solution would not be recommended for an enterprise or any shop where you have multiple developers working on the same solution.

Incentivized

There is really no real reason why not to use Yarn today. It's much faster than npm, and you will need a dependency management system anyway. The only thing that might be missing is the fact that it doesn't come natively with NodeJS, and you have to install it yourself. I'd like to see the NodeJS ecosystem include Yarn by default.

Incentivized

• avoid losing code
• versioning of previous projects
• saving versions on db

Incentivized

• Package management
• Speed of download compared to npm
• Moduel version control

Incentivized

• Becoming corrupt and having to be rebuild from a previous version.
• It can be extremely slow to check in & out of.
• Lost support several years ago from Microsoft.

• Rarely, some server connection error appear, while npm works alright.
• Sometimes, deleting the whole vendor directory is the best solution to solve weird issues.
• You still might need npm to install Yarn.

Incentivized

Overall Microsoft Visual Source Safe is very easy to use. It is a simple application that does only one thing. It has the basic windows tree structure for listing projects and solutions. There is no way to search for a particular file, project or solution. There is also no way to search the code in the files.

Incentivized

There is no longer support for Visual SourceSafe as I believe it's been retired. There are, however, users that still use the tool and they do help if there are questions or complaints.

Azure DevOps is a much better, more modern tool that Visual SourceSafe and everyone should be moving to it. Most if not all the integration that is there can be done or emulated in it

Compared to npm, Yarn is a clear winner here. npm does not look to be getting any improvements recently. And it's much much slower to run when installing project dependencies. This has a clear impact on the developer productivity but also makes deployments slower. So Yarn is still a much superior choice.

Incentivized

• When we started using it, it allowed us to do source code versioning and store the code in a centralized location and not locally.
• We are using it for very few projects with few developers that still maintain those applications and do not have time to merge the source code to Git.

Incentivized

• Deployments happen much faster.
• Building and testing our apps is much more streamlined and efficient.
• Makes it easier to write reusable code.

Incentivized