Before GitHub

2026-04-28 · Source: Armin Ronacher's Thoughts and Writings · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure · Depth: Intermediate, long

Summary

The author reflects on the evolution of Open Source software development, contrasting the pre-GitHub era with the platform's rise and current perceived decline. Before GitHub, projects often ran on self-hosted infrastructure like Trac and Subversion, fostering a smaller, more reputation-driven community where dependencies were carefully considered. GitHub centralized this, making project creation, discovery, and contribution frictionless, leading to an explosion of micro-dependencies and forming a significant part of the Open Source social infrastructure. While acknowledging GitHub's immense contributions, such as archival work and normalizing open collaboration, the author expresses concern over its current instability, product churn, and unclear leadership, which are causing prominent projects like Ghostty, Strudel, and Tenacity to consider moving. This shift away from GitHub, while potentially decentralizing and restoring autonomy, risks losing valuable social context and historical data if not properly archived.

Key takeaway

For CTOs and VPs of Engineering evaluating their Open Source strategy, recognize that relying solely on a single commercial platform like GitHub for project hosting and archival introduces significant risk. Actively explore and support decentralized alternatives and public archiving initiatives to ensure the long-term discoverability and preservation of your projects' code, issues, and social context, mitigating the impact of platform instability or business model shifts on your software supply chain.

Key insights

Centralized platforms like GitHub profoundly shaped Open Source, but their decline necessitates new archival solutions.

Principles

• Centralization creates discoverable memory.
• Frictionless publishing leads to dependency explosion.
• Distributed systems can still centralize around services.

In practice

• Mirror social context of projects.
• Preserve release artifacts and metadata.
• Support public Open Source archives.

Topics

• GitHub
• Open-Source Ecosystem
• Code Hosting Platforms
• Software Dependencies
• Distributed Version Control

Best for: CTO, VP of Engineering/Data, AI Architect, Software Engineer, Director of AI/ML, Research Scientist

Related on AIssential

• The Repository Revolution: Powering Collaboration in Tech — Repositories centralize data and code, providing version control essential for modern software development.
• Is Open Source Dying? — AI contributions and legal replication services are fundamentally reshaping open-source software's purpose and sustainability.
• The Pulse: AI load breaks GitHub – why not other vendors? — GitHub's severe reliability issues stem from under-preparedness for AI-driven load spikes and complex infrastructure migration.
• GitHub Uses eBPF to Eliminate Deployment Risks and Prevent Circular Failures — eBPF enables kernel-level network control to prevent circular deployment dependencies and enhance system resilience.
• 10 GitHub Repositories to Master Self-Hosting — GitHub repositories offer practical, project-based learning for mastering self-hosting and modern infrastructure.
• The Pulse: AI load breaks GitHub – why not other vendors? — Increased AI-driven load is impacting core developer infrastructure reliability and business models.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Armin Ronacher's Thoughts and Writings.