Hacker News new | ask | show | jobs
by nightfader 1000 days ago
That's what object storage with versioning turned on is for e.g. GCS or S3
2 comments

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.
Why use git at all then? Just use an object store with versioning turned on.
Because git excels in relatively small size text files and patching and difficult. You can't binary blobs like jpegs, audio, video easily.
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.