Open source before GitHub meant reputation-gated dependencies, self-hosted forges, and infrastructure you personally operated; GitHub collapsed all that friction and now its decline threatens the trust layer it became.
Key Takeaways
Pre-GitHub, dependencies implied real due diligence: SourceForge, self-hosted Trac and Subversion, vendored code, and mailing lists enforced accountability by friction.
GitHub’s biggest underrated contribution was archival: abandoned projects stayed findable, forks and issues stayed online, unlike personal VPS setups that vanished when domains expired.
The distributed-VCS irony: Git and Mercurial were philosophically decentralized, yet the world standardized on one centralized GitHub, recreating the problem they were meant to solve.
GitHub’s trust role extended beyond source hosting into npm trusted publishing; erosion of GitHub trust now damages the entire supply chain, not just code discovery.
The author calls for a public, endowment-funded archive for source code, release artifacts, and project metadata, independent of any company’s business model.
Hacker News Comment Review
Commenters split on whether GitHub’s archival dominance was net positive: one strand argues centralization atrophied collective archival instincts and created false confidence in preservation.
Several commenters pushed back on the author’s dismissal of Codeberg, noting its non-profit legal structure makes it more mission-aligned for FOSS than a Microsoft subsidiary, calling for-profit free infrastructure a zero-interest-rate artifact.
Fossil drew strong advocacy as the road-not-taken: its single-file model bundles wiki, tickets, and forums with the repo, keeping project context versioned and portable in ways GitHub never attempted.
Notable Comments
@dolmen: Points to Software Heritage (softwareheritage.org) as an already-existing European public archive that fits the author’s proposed mandate exactly.
@alastairp: GitHub’s person-centric repo model, vs. SourceForge’s project-reservation ceremony, was what actually lowered the psychological barrier to publishing.
@pistoriusp: Flags code.google.com as the clearest historical lesson in how fast a well-resourced platform can vanish and take context with it.
