It's not about any one thing. It's a thought experiment about the moral compromises societies make, and the emotional responses people have toward such compromises.
they are talking about rules specifically set for some class retirement funds, which some 401k adopt. Those were set in place most to make sure syndicate run funds were playing nice.
nothing to do with your techie 401k were anything resembling even the word syndicate won't apply.
Are you saying storing pointers to large files isn't sane to do in Git? What are your suggested solution for dealing with large assets you want versioned and easily accessible?
If you're really dogmatic about it, I guess you would have no dependency lock files either, but commit all that code directly to git instead of having references. Some people do that, so wouldn't be a huge surprise.
It means that the large majority of projects that don't use git-lfs can improve their security immediately and without any trouble.
It also may mean that git-shell could use a few PRs adding whatever is missing for git-lfs to work, given that git-lfs does not do anything extra fancy.
use something that can actually version your large files. git-lfs is silly and trying too hard. it's the literal faster horse of file versioning. it's so wrong by design i don't even know where to start.
anyone remember when one of those dna testing companies was offering free dna testings in some atlanta(?) neighborhood, but then someone found out it was being paid by the local PD to try to find dna that matched someone they were looking for?
I'm certain i read about it from HN but i can't find any reference to that new anymore.
IT data destruction companies all remove the storage, and put the device back on ebay the same day.