9 engineers on Hacker News describe using Git LFS first-hand: 1 endorse it, 6 regret it, 0 are mixed.
“The LFS process was certainly better than the other alternatives... but it was still not ideal.”
regret · production · danudey · 2026-06-17 · source ↗ · wrong label?“git-lfs is a nightmare. Two projects at $lastco used it. It's more trouble than it's worth.”
regret · production · kortex · 2021-12-21 · source ↗ · wrong label?“with git-lfs, which is also a (mild) pain.”
regret · production · dilap · 2020-12-21 · source ↗ · wrong label?“I've been using GIT LFS for the last 6 months with an Unreal Engine project... it really is painless.”
endorse · personal · 0.5 yr · fit2rule · 2019-12-22 · source ↗ · wrong label?“Yeah I didn't have much luck with LFS but we didn't really need it so it wasn't a problem to just disable.”
regret · production · lttlrck · 2018-05-07 · source ↗ · wrong label?“Git-LFS is a bit a pain to setup, because you need to define before checking in, which extensions need to be stored as large file.”
regret · personal · zubspace · 2017-12-03 · source ↗ · wrong label?“without SSH and with all its numerous bugs LFS is one of the worst pieces of software i've come across.”
regret · production · woodcut · 2016-08-05 · source ↗ · wrong label?“Git-LFS is configured and all large files are correctly checked out”
neutral · production · pxc · 2025-12-15 · source ↗ · wrong label?“we use LFS aggressively which can get pricey on GitHub but I'm happy to pay for usage”
neutral · production · lazypenguin · 2023-03-02 · source ↗ · wrong label?