1. Git's Unsuitability for Large-Scale Package Management
Git excels for source code but struggles with package registries due to inefficient protocols and GitHub limits.
"Most of the problems mentioned in the article are not problems with using a content-addressed tree like git... The problems are with gitβs protocol and GitHubβs implementation thereof." β amluto
"Git knows how to store [a hash-addressed tree], but git does not know how to transfer it efficiently." β mananaysiempre
2. "Tragedy of the Commons" Debate on GitHub Overuse
Heavy reliance on free GitHub hosting risks limits or changes, likened to overexploiting shared resources despite MS ownership.
"This seems like a tragedy of the commons -- GitHub is free after all, and it has all of these great properties, so why not?" β c-linkage
"Anything that is free to use is a commons, regardless of ownership, and when some people use too much, everyone loses access." β dahart
3. Pragmatic Iteration Over Upfront Scaling in OSS
Volunteer devs defend starting simple with Git and fixing scaling later, rejecting "lazy" or unethical labels.
"Do the easy thing while it works, and when it stops working, fix the problem." β ekjhgkejhgk
"Fixing problems as they appear is unethical? Ok then... Some people would argue that if you keep working on problems you don't have but might have, you end up never finishing anything." β ekjhgkejhgk