A little disappointed to see no mention of https://git-lfs.com/ – which, IIUC, is the most official solution. Maybe it doesn’t count because you need a separate backing store?
git-lfs is an entirely different class of solution that doesn’t address the actual concerns that are outlined in the article. It works by simply replacing files that match the patterns in .gitattributes with place holder pointers to files held in another storage backend that doesn’t concern itself with any of the rest of git’s features.
The ZFS mention is interesting because ZFS can do this unidirectionally. The missing thing is a merge feature and that’s always the hard part: if two people edit the same file, what do you do? The git solution is roughly the same as CODA: provide per-file type plugins to handle the merging, with line-diffs and merge as the fallback (which can be very wrong even for text-based source code: one person renames a function, another adds a call to the function elsewhere, no merge conflicts).
A little disappointed to see no mention of https://git-lfs.com/ – which, IIUC, is the most official solution. Maybe it doesn’t count because you need a separate backing store?
git-lfsis an entirely different class of solution that doesn’t address the actual concerns that are outlined in the article. It works by simply replacing files that match the patterns in.gitattributeswith place holder pointers to files held in another storage backend that doesn’t concern itself with any of the rest of git’s features.Some tools usually used for this kind of thing: Rclone, Rsync, Restic, Syncthing
The ZFS mention is interesting because ZFS can do this unidirectionally. The missing thing is a merge feature and that’s always the hard part: if two people edit the same file, what do you do? The git solution is roughly the same as CODA: provide per-file type plugins to handle the merging, with line-diffs and merge as the fallback (which can be very wrong even for text-based source code: one person renames a function, another adds a call to the function elsewhere, no merge conflicts).