As a game developer, my repository is many gigabytes in size - consisting mostly of binary data. Perforce handles it like a champ; it scales incredibly well, even to the near-ridiculous volumes of data I need to build my projects.
And first hit on a quick search: It is well known that Google uses Perforce as its internal source management system (it has a source license).
So, obviously, it should be prescribed that everybody and his dog use a DVCS good at merging changes on text files, which solves the problem of the subset of people that:
1 - Hop around like rabbits, carrying their copy of the whole repository, and previously had to mail each other patches.
2 - Only work on text files, code with barely any non-text documentation, like top-dog kernel developers.
http://www.reddit.com/r/programming/comments/biv72/why_git_a...
As a game developer, my repository is many gigabytes in size - consisting mostly of binary data. Perforce handles it like a champ; it scales incredibly well, even to the near-ridiculous volumes of data I need to build my projects.
And first hit on a quick search: It is well known that Google uses Perforce as its internal source management system (it has a source license).
So, obviously, it should be prescribed that everybody and his dog use a DVCS good at merging changes on text files, which solves the problem of the subset of people that:
1 - Hop around like rabbits, carrying their copy of the whole repository, and previously had to mail each other patches.
2 - Only work on text files, code with barely any non-text documentation, like top-dog kernel developers.
Good going.