Version Control Systems


Visual SourceSafe vs SVN

  1. This system is likely to be a passing fad.

    75% 25%
  2. This system is easy to learn.

    39% 61%
  3. This system has a model which is easy to understand.

    36% 64%
  4. This system is easy to use.

    28% 72%
  5. This system has good GUI tools.

    23% 77%
  6. I am familiar with this system.

    23% 77%
  7. This system is good for small teams.

    18% 82%
  8. This system is easy to administrate.

    17% 83%
  9. This system is good for working offline.

    17% 83%
  10. This system is good for binary files.

    13% 87%
  11. This system has good integration with other tools.

    11% 89%
  12. This system has good tools for importing from other VCSs.

    10% 90%
  13. This system is good at merging.

    8% 92%
  14. This system is good for large teams.

    7% 93%
  15. This system is good for dispersed teams.

    6% 94%
  16. This system is robust against data loss.

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

    4% 96%
  18. This system is pluggable.

    4% 96%
  19. This system is good at branching.

    4% 96%
  20. There are good hosting services for this system.

    2% 98%
  21. Many project hosting services support this system.

    2% 98%

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 Visual SourceSafe and SVN 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.