Is a DVCS useful for one developer?

Question

Or would a conventional client-server VCS be more appropriate? I\'m currently using TortoiseSVN, but I\'m interested in a DVCS, but I\'m not sure if it\'s even a good idea to tr

Answer 1

I seriously recommend going with a distributed one. On Windows, I chose Mercurial and have been very happy with it.

Big pros:

• Local commits are fast, can commit often (Test, Code, Refactor, Commit)
• Branching is simple
• You can commit wherever you are.
• Simple to move files around (No more mess like I use to get into with SVN)
• Just simpler. One software does it all (including admin tasks)
• File system is cleaner. No more .svn everywhere, just one folder
• List of ignored files is just another file in the repository and gets automatically copied to every clone. Easier to keep clean than SVN again.
• Bitbucket.com is nice and gives one free private repository

Cons:

• (For some) GUI tools are not there
• You will probably need SVN still to connect to various source repositories. E.g. need to use two systems.