A very useful link there. Quite pragmatic. It tells us that Subversion's experts believe its future lies in:
- "Huge projects where putting all the current source code on everyone's machine is infeasible."
- systems with very complicated permission schemes where "you just plain aren't allowed to give everyone all the data"
- "organizations whose users need to interact with repositories in complex ways... These things are probably most useful to the corporate world, and to governmental and military organizations." [Karl Fogel]
So, if you recognize yourself in any of those groups, learn SVN. But otherwise I'd start with git. You can pick up the necessary rudiments of SVN (or, god help me, CVS) later when you need them.
- "Huge projects where putting all the current source code on everyone's machine is infeasible."
- systems with very complicated permission schemes where "you just plain aren't allowed to give everyone all the data"
- "organizations whose users need to interact with repositories in complex ways... These things are probably most useful to the corporate world, and to governmental and military organizations." [Karl Fogel]
So, if you recognize yourself in any of those groups, learn SVN. But otherwise I'd start with git. You can pick up the necessary rudiments of SVN (or, god help me, CVS) later when you need them.