Q. Vault > Subversion, why?
Not a burning issue, but someone was presumably all hopped up on free beer/free software, and begged the question “why is your expen$ive vault so precious? why is it named vault, because it's lock-in loving users keep all of their ill-gotten dollars in it? software just wants to be free, captalist oppressor...”
I'm paraphrasing but enjoying myself. But there was a notable lack of capitalization, so whatever.
Anyway, I alleged that was the relative pecking order for one reason only: Vault does advisory locks when in commit-copy-merge mode, svn doesn't yet. So it can't really do much to prevent collisions on managed binary assets... which is a problem if you're working with it on a distributive team with monolithic assets. It's planned for a future release of svn although the roadmap didn't seem clear as whether or not this was near or far in terms of horizons.