SVN has been working just fine for my group for a number of years. We have a total of about 35 people across 7 or 8 teams using the same set of repos and build server. We've discussed moving to git because our dev organisation use it, but if and when we do, we'll probably continue to use SVN as our front end, because git introduces complexities that most of us simply do not need in our day-to-day work. We sometimes branch but very seldom merge. (*My* job unfortunately includes the major exception to the latter case, but due to the nature of things, I'm *always* going to be stuck with doing this manually no matter what CVS we use. BTW, SVN rocks when it comes to performing reverse merges when you've committed something stupid and just need it to go away ASAP.)
We use SVN in maintaining both the huge set of docs for which we're responsible (XML plus pulls from software sources plus various other text and binary assets) plus the backend for processing them (Perl, Python, PHP, ruby, shell, XSLT, FOP, javadoc, Doxygen, heaps of Makefiles, etc.) and it does just great.