2 ms·
There are a few reasons why you might want to start out with SVN rather than git: * It's simpler (though admittedly the complex and confusing features of git r
by brazzy 16y ago
There are a few reasons why you might want to start out with SVN rather than git:
* It's simpler (though admittedly the complex and confusing features of git really only become relevant when there are multiple developers).
* If you're going to work for corporate clients with their own repositories, chances are very high it's going to be SVN (it's possible to use both via the git-svn tool, but that adds more complexity)
That being said, git does have a number of very nice features that are useful to lone developers as well.
- bradleyland 16y agoIf you're eventually going to move to something like Git or Hg, you really ought to skip SVN all together. The concepts you learn in SVN will make Git or Hg seem counter intuitive, and the Git / Hg model is a better way to work once you start using teams.
- brazzy 16y agoMy (second) point was that there's a good chance you won't be able to skip SVN anyway.