out of the box large file support requires one central repository.
How so? As far as I know, git doesn't treat large files any differently than small ones.
How so? As far as I know, git doesn't treat large files any differently than small ones.
As far as I know git isn't good at storing binary data. Git depends on line breaks to be able to diff and make change sets. If you store a binary file in git and make an update to it - even though that update only changed 1 byte, the entire new version of the file is stored again. Dat uses Rabin fingerprinting to intelligently slice binary files into chunks that are less likely to change. That make dat a lot more efficient at storing, versioning, and syncing videos, images, and other large binary files.
Other than that, Git treating large files the same as small ones is part of the problem, and the reason that centralized extensions exist. You wouldn't want "git clone" to clone the complete history of every large file, while that's not a concern at all for small files.
When comparing to Dat, I don't see how; you can't push any Dat repository to Github.
Other than that, Git treating large files the same as small ones is part of the problem, and the reason that centralized extensions exist. You wouldn't want "git clone" to clone the complete history of every large file, while that's not a concern at all for small files.
You don't need centralized extensions for that, though. I use git-annex, which is completely P2P.
Good luck with git-annex.