Programming Circlejerk

161 readers

20 users here now

Community to talk about enlightened programming takes

Rules:

read and follow the programming.dev code of conduct
no flamewars
mark your unjerks
only programming related content allowed
link to the original source
do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.

founded 2 months ago

MODERATORS

[email protected]

Every developer had their own sacred list of Git rituals they swore were "the good ones," like medieval doctors prescribing bloodletting. (www.linkedin.com)

submitted 1 day ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 10 hours ago

they're putting large amounts of binary data in git lfs, which is what it was designed for. lfs does have some rough edges though. if I had something really heavy on binary blobs, ex a large game or similar, idk if I'd be using git either. he extrapolates way too far though, most use cases don't run into any of these problems

and storing all that in a separate db is insane, it's stuff that should be versioned with the code. it's likely being created at a specific rev for the current code, and it evolves with it. if you git revert or create a pr, it should be part of that. it's not like they committed built binaries or smth. there should be tools able to handle this. git could be one of them if lfs was less rough