Version Control Systems


SVN vs Visual SourceSafe

  1. Many project hosting services support this system.

    97% 3%
  2. There are good hosting services for this system.

    97% 3%
  3. This system is good at branching.

    95% 5%
  4. This system is pluggable.

    95% 5%
  5. There is a good community around this system.

    95% 5%
  6. This system is robust against data loss.

    94% 6%
  7. This system is good for dispersed teams.

    93% 7%
  8. This system is good for large teams.

    92% 8%
  9. This system is good at merging.

    91% 9%
  10. This system has good tools for importing from other VCSs.

    89% 11%
  11. This system has good integration with other tools.

    88% 12%
  12. This system is good for binary files.

    86% 14%
  13. This system is easy to administrate.

    82% 18%
  14. This system is good for working offline.

    82% 18%
  15. This system is good for small teams.

    81% 19%
  16. I am familiar with this system.

    76% 24%
  17. This system has good GUI tools.

    76% 24%
  18. This system is easy to use.

    71% 29%
  19. This system has a model which is easy to understand.

    63% 37%
  20. This system is easy to learn.

    60% 40%
  21. This system is likely to be a passing fad.

    24% 76%

What's going on here?

The absolute rankings are interesting for large scale comparisons but when you want to know about two specific languages it's much more informative to look at how the two fare when they go directly head to head.

Here are all the statements which we've got enough comparisons between SVN and Visual SourceSafe to be meaningful and which of the two our users picked.

The order in which we're presenting them is a little arbitrary (sorry), but we've tried to put the things which they're both good at first so as to give you the most interesting picture of it.