Re:Fossil versus Git
by nightfader on Saturday September 23, 2023 @08:36AM
(#37622724)
That's what object storage with versioning turned on is for e.g. GCS or S3
[ Parent
| on HN ]
Re:Fossil versus Git
by sausagefeet on Saturday September 23, 2023 @08:43AM
(#37622748)
Why use git at all then? Just use an object store with versioning turned on.
Re:Fossil versus Git
by nightfader on Saturday September 23, 2023 @08:47AM
(#37622778)
Because git excels in relatively small size text files and patching and difficult. You can't binary blobs like jpegs, audio, video easily.
Re:Fossil versus Git
by sausagefeet on Saturday September 23, 2023 @05:06PM
(#37627558)
But that's my point: why can't a version control system be good for this as well? It's the same thing underneath. Why do we have to split these different use cases across different tools and hope a foreign key constraint holds?
We've got lots of disk-backup tools that handle this just fine, deduplicating blocks and compressing where they're able.
Re:Fossil versus Git
by gchamonlive on Saturday September 23, 2023 @08:47AM
(#37622780)
Although blob storage work well for versioning, you have to make heavy use of the underlying proprietary API to get these versions, and I am not quite sure you can do more complex operations, like diff and bisect between those versions the way you could with git.