I don't know if you're being sarcastic or not, but I'll assume it's an innocent question: Yes, there are huge numbers of people still using SVN.
SVN is a mature, easy, and simple solution. Git is wonderful, but all the improvements it brings aren't enough to actually convince IT departments to upgrade years of SVN over to Git (or to bother installing the Git-SVN bridge).
SVN gets the job done. With teams of under 10 developers on each project, SVN just works. There isn't a real bleeding need for Git's featureset, and especially if you've never used them, you probably don't know what you're missing out on. But the truth is, the answer to that is not much.
I know and have personally upgraded companies from SourceSafe to SVN..... after DVCS caught on. Sometimes the simpler solution is the safer bet, drastic change isn't always the answer and is never good for productivity, especially against a deadline as most companies and dev teams seem to be doing these days.
For myself, as a one-man dev team on projects with multiple simultaneous branches and 100k+ LOC and dozens of modules cross-linked and cross-developed......... SVN still gets the job done :)
> But the truth is, the answer to that is not much.
This claim may sound like truthful only if one never
used git indeed.
EDIT: I think I should expand this. There is what I would miss if git is taken away from me, in no particular order:
Speed, speed, speed. Operations which SVN performs over network (and not
in the most efficient way) git performs locally and it's blazingly fast.
Ease of branching and merging.
Local branches, squash commits.
Rebase.
Staging area.
Stash.
Having entire history at my fingertips and not having single point of failure which SVN central server is. The fact that entire history in git often takes less space than single checkout of SVN is a nice bonus.
Not having each and every directory of my project littered with .svn
Github.
There is more, of course.
I was kind of Subversion fan when I first saw Linus talk on git (http://www.youtube.com/watch?v=4XpnKHJAok8 ) and I did not like it at all. Then I did try git and saw the light :)
I am still using SVN, but only because I have to. Now it looks dated (mature?), slow, clunky and fragile.
Git is a blub. Compared to nothing svn is awesome! It is more then just the distributed nature. There are so many features that Git brings over older revision control systems that if I was forced to use an old one (and not allowed to use git-svn or something) I would change jobs. I can simply be way more productive with Git.
I agree. And for me, the awesomeness didn't really sink in from reading the documentation. I had to actually use it to be won over. Whereas, if you've used CVS, SVN is a breath of fresh air, but it just doesn't blow you away.
This is provocative comment. I use svn every day. It seems to meet all my needs. I find it logical, fast enough, tags, branches, and merging make sense, etc. When I started hearing about git, I looked at the docs and a couple of tutorials, and my conclusion was that it was esoteric. Nothing stood out as "wow that would be really cool" or "wow that's something I have wished I could do but svn doesn't let me". If it's "fast" that's nice, but not enough of a reason for me to switch; I don't feel like my productivity is really hampered very much waiting for svn operations. So, I never actually tried using git.
But, your remarks have intrigued me, so I might give it a try on a couple of personal projects I want to get done.
The awesomeness starts from git init; git add . (or in my case, hg init; hg add). Even if you don't use anything else, this is a big improvement over Subversion.
(The pg article that coined "Blub" (http://www.paulgraham.com/avg.html) uses it as the name of a middle of the road language between machine language on the low end of the power scale and Lisp on the high end. So Blub is to Lisp as SVN is to Git.)
SVN is a mature, easy, and simple solution. Git is wonderful, but all the improvements it brings aren't enough to actually convince IT departments to upgrade years of SVN over to Git (or to bother installing the Git-SVN bridge).
SVN gets the job done. With teams of under 10 developers on each project, SVN just works. There isn't a real bleeding need for Git's featureset, and especially if you've never used them, you probably don't know what you're missing out on. But the truth is, the answer to that is not much.
I know and have personally upgraded companies from SourceSafe to SVN..... after DVCS caught on. Sometimes the simpler solution is the safer bet, drastic change isn't always the answer and is never good for productivity, especially against a deadline as most companies and dev teams seem to be doing these days.
For myself, as a one-man dev team on projects with multiple simultaneous branches and 100k+ LOC and dozens of modules cross-linked and cross-developed......... SVN still gets the job done :)