undefined | Better HN

0 pointssyndicatedjelly2y ago0 comments

Does Git LFS help with this problem?

0 comments

Overall LFS feels a very hacky tacked on solution with warts.

Git LFS is horrible if you mistakenly add some file(s) to LFS.

Restoring to LFS-less state is supposed to be easy but it is always very painful.

There should be a way to tell repo - I do not want any LFS at all. In practice this is painful, and it is easier to start a new repo....

Also for some reason Github/Microsoft decided to "monetize" LFS. The freebie limits are 1GB for hosting AND transfer! Then the charges get very expensive.

I am not sure why Github LFS is priced like some AWS S3 plan not OneDrive plan.

vtbassmatt2y ago

GitHub charges for LFS and has since they initially introduced it, way before Microsoft was involved. Also, the pricing model is changing and will include a minimum of 10GiB for free (250GiB for Team/Enterprise customers). It’s cost-recovery and abuse-prevention, though, not some nefarious scheme. And funny you mention AWS S3... what costs might GitHub be recovering? ;)

Microsoft’s homegrown LFS implementation (in Azure DevOps) does not and has never charged for LFS. It’s nice to have friends with a cloud blob storage service!

Source: I was the product manager for Azure Repos’s LFS server and am currently the product manager for all things Git at GitHub.

robaato2y ago

Have seen various teams have major issues with LFS - becoming quite a support overhead to keep art teams productive.

flohofwoe2y ago

Yeah exactly this. Git LFS is supposed to fix the problem, but I haven't seen it working flawlessly either yet.

syndicatedjellyOP2y ago

Interesting, I had issues using Git LFS to store images for my personal site. I thought I just didn't know how to use it properly...

jzl2y ago

Not Git LFS, but Git VFS, now replaced by “Scalar”:

https://github.com/microsoft/scalar

j / k navigate · click thread line to collapse