The tl;dr is that "xet" is like GitLFS (it stores pointers in Git, with the data in a remote server and uses smudge filters to make this transparent) with some additional features:
- Automatically includes all files >256KB in size
- By default data is de-duplicated 16KB chunks instead of whole files (with the ability to customize this per file type).
- Has a "mount" command to allow read-only browse without downloading
When launching on HN it would be better if the team was a bit more transparent with the internals. I get that "we made a better GitLFS" doesn't market as well. But you can couple that with a credible vision and story about how you are a better and where you are headed next. Instead this is mostly closer to market speak of "trust our magic solution to solve your problem".
These details seemed.... really clear to me from the post the OP made? Did you just not read it, or have they updated it since you commented?
(excerpt from the OP post:
> Unlike Git LFS, we don’t just store the files. We use content-defined chunking and Merkle Trees to dedupe against everything in history. This allows small changes in large files to be stored compactly. Read more here: https://xethub.com/assets/docs/how-xet-deduplication-works)
- Automatically includes all files >256KB in size
- By default data is de-duplicated 16KB chunks instead of whole files (with the ability to customize this per file type).
- Has a "mount" command to allow read-only browse without downloading
When launching on HN it would be better if the team was a bit more transparent with the internals. I get that "we made a better GitLFS" doesn't market as well. But you can couple that with a credible vision and story about how you are a better and where you are headed next. Instead this is mostly closer to market speak of "trust our magic solution to solve your problem".