Re: SVN will never beat GIT
I just wish GIT would finally implement the stuff that make SVN so practical. We recently had the eternal discussion about git vs SVN again. I'm not a SVN fanboy, but it does irk when every argument against is countered with a "you shouldn't want that, DVCS is a different world" etc etc, without a list of concrete issues.
1. global revision versions instead of not sequential unwieldy guids or urls. revisions are easy to communicate with, and reach across branches.
2. partial checkouts (needed depending on if the solution to (3) is to stuff everything in a giant repo)
4. one should be able to mark certain branches that never should have mutliple heads. (fixes and other stability branches)
5. decent merge tracking of what is merged to which branch. cherry picks already fail if you need some minor editing to merger.
(6.) lineendings handling. Lineendings in the repo should never be an issue and human error should be minimized (no client setup or post commit hook fiddling required etc). There was some movement on this in GIT since the last discussion, so it might be solved. Didn't get a practical evaluation of the current state though, so I put it in parenthesis
It is not just BSD, teams like GCC and LLVM are afaik still using SVN as well.