the achilles heel of svn is branches cost 100% of the branched repository. even an svn repo with one user can be prohibitively large.
even in a corporate lan environment just pulling down an svn repository can take far too long
even in a corporate lan environment just pulling down an svn repository can take far too long
http://stackoverflow.com/questions/2041/how-do-i-create-a-br...
svn doesn't fit the sane modern workflow and everything it does can be done by git in a less painful manner. I think the only use case I can think of for svn is a very binary heavy repo that needs global locking.
You can have two separate copies checked out, but you don't have to.