No, please don't even bother.
Seriously, start from a DVCS. The fact that SVN is popular doesn't make it the standard. Linus Torvalds would tell you that it might rot your brain.
Read this great article/introduction by Joel Spolsky called Subversion Re-education.
You might also be interested in reading this other question: I'm a Subversion geek, why I should consider or not consider Mercurial or Git or any other DVCS?
Choosing between DVCSs
Personally, I use both mercurial and git, and I think that it is important to know both. A recommended reading about this is Git vs. Mercurial: Please Relax (see the git-addremove example). Two quotes from that article that I think sum it up.
Git’s design philosophy is
unmistakably that of Unix: unlike
Subversion, CVS, or Mercurial, git is
not one monolithic binary but a
multitude of individual tools, ranging
from high-level “porcelain” commands
such as git-pull, git-merge, and
git-checkout to low-level “plumbing”
commands such as git-apply,
git-hash-object and git-merge-file.
So, like MacGyver, you can do just
about anything you need with Git –
this includes totally awesome Wiki
engines, issue trackers, filesystems,
sysadmin tools – everything short of
Developers who like to keep their
system clean will probably appreciate
the fact that hg installs one binary
in contrast to the 144 that make up
git, and developers who think that
git’s ability to edit your previous
commits is moronic, unnecessary, and
dangerous will appreciate the
simplicity hg provides by omitting
that particular feature.
A lot of projects can be found on github and git is more powerful, but it can also be somewhat intimidating to newcomers, specially windows users. There is also bitbucket (github's equivalent for mercurial).
My recommendation: start with mercurial and as soon as you feel comfortable with it, pick up git; it is not about the tools, it is about the people you work with.
What I consider subversion's real and practical use is, not for working with other people, but for perhaps to implement an updater for your production applications, here is why:
- Currently, svn is almost installed in most hosting providers
- Has good subproject support (addressable in git and hg now, though).
svn up and your project and its dependencies get updated.
Quoting Thorbjørn on this other thread:
DVCSes are to Subversion, what
Bittorrent is to ftp
Edit: If there is a VCS you should know before Git, that could be Mercurial (way more friendly CLI interface and good to get introduced to the distributed concepts). This advice applies specially to those coming from Subversion since the CLI is also similar in some degree. Distributed Version Control can be easier to learn than Centralized Version Control, since you just worry about your repository instance, and not the client and server parts in separate.