Git/Mercurial/etc don't provide the strong locking mechanisms needed to deal with binary files.
Combine that with the fact that Git falls over at ~5GB. When I was in games we'd regularly have repos > 30GB for a code sync or > 150GB for art sync.
Perforce would pull down that art sync in 10 minutes, good luck doing that with Git, not to mention that they support Proxies that handle caching of large changesets automatically for remote teams.
I know Perforce is making a killing off of this market. People here are always asking for startup opportunities... so I would suggest collaboration on large binary files for artists. Not that I really know what strategy to take, but I smell something funny when one company has dominated a niche for over a decade. If you want to be glib you can call it Github for artists :) I guess they do use Dropbox for collaboration already though.
I've never heard that (and certainly don't personally deal w/ git repos that large). I thought massive repository handling was supposed to be a strength of git. How does git (start) failing at that scale ?
http://thread.gmane.org/gmane.comp.version-control.git/18977...
So they are patching Mercurial, apparently with some Google collaboration (!)
https://code.facebook.com/posts/218678814984400/scaling-merc...