4 ms·
Honestly, I'd just trawl the interwebs for all the reasons folks have had grief with LFS, and then see if Oxen can even do a fraction better. If it can, you'll
by Zee2 4y ago
Honestly, I'd just trawl the interwebs for all the reasons folks have had grief with LFS, and then see if Oxen can even do a fraction better. If it can, you'll have many billion-dollar companies that would be highly interested in your solution :)
A few starting points from personal experience would be
- Ensuring git-aware code editors don't try and mangle blob histories when they encounter them
- Modern, high-performance blob downloads/version-resolution
- Human-readable/debuggable meta-files, where it's easy to recover from bad states (instead of an opaque empty file with a GUID...?)
- yarg 4y agoIf you want blob support, you'd probably need to introduce format specific understanding of file structures. You'd also need for the blob encoder to be exceptionally stable - if minor changes to the input lead to significant changes to output, you're going to have a lot of trouble. Something like Google's Courgette (binary patch generation) could help to simplify things, but an old thread mentioned a patent suit. https://news.ycombinator.com/item?id=2576878 https://news.ycombinator.com/item?id=2576878
- bfm 4y agoShameless plug. I open-sourced https://snapdir.org/ https://snapdir.org/ to explore how to solve these exact issues. It's an early prototype to gather feedback around the ergonomics of the interface and the manifest format, and I would love to learn if people might find it useful enough for the use cases where LFS falls short.