Visual SourceSafe (Discontinued) vs. Yarn

I would not recommend Visual SourceSafe to anyone out there as there are so many better, more modern solutions that do what it does and much more. Visual SourceSafe should be retired in most cases.

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

• At this point in its lifecycle there are not many things VSS does well
• Its main strength would be its ability to be self contained on a local drive
• It is a basic Code repository

Incentivized

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

Incentivized

• The system stability could be improved. Often we get file corrupted errors.
• The User Interface is not modern and not user-friendly.
• Concurrent check-outs could be added, allowing more people to work on the same file at the same time.
• Add conflict resolution, files comparison, blame file, features that any modern source control program should have.

Incentivized

• 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

The current status of Visual SourceSafe is not usable. There are many things that are just so out of the date that it should be retired and not looked at any longer. If you have an existing application that is stored in it, I'd consider migrating it to a modern tool.

It's a Microsoft product so the customer support is great. The program has been around a long time so there are plenty of places on line to get assistance. Also almost any development shop you go to will have at least one developer who has used this product extensively in their career.

Incentivized

Incentivized

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