What is the best version control software for lone web developers?
patio11: The most important thing: ANY source control is better than NO source control.  It is 10,000 times more important that you pick one package, learn it, and USE IT than you pick any particular package.  (Source control isn't useful until you've made it a routine part of the workflow.)I use SVN, because that is what I got started on and that is what I know.  It works fine, for allowing me to go back to known-good versions of the code, and for allowing stupidly easy Rails deployments through Capistrano.  But really, any of the alternatives are probably just as fine.[Incidentally, my repositories sits on a machine that gets backed up daily.  That is, similarly, a good-enough-for-now solution.  There are other alternatives: use a dedicated provider, put it on a machine other than the deployment machine, use distributed source control, whatever.  Any of them works as long as the answer is not "source control on the same machine you spend most of your time on", and heck, that still captures a good deal of the source control benefit, come to think of it.]