GitHub has alternatives, but no replacement
GitHub’s dominance as a code hosting platform is seen as resting less on git itself and more on powerful network effects, generous free CI runners—especially for Windows and macOS—and low-friction contribution workflows. Commenters explore alternatives like Forgejo, Codeberg, Sourcehut, Radicle, Tangled and self-hosted setups, but note trade-offs in reliability, maintenance burden, discoverability, federation, and policies such as AI-generated code bans. Many conclude that while technical replacements for GitHub’s core features exist, its social coding ecosystem and free infrastructure remain hard to fully replicate.
Free CI and compute as primary lock-in
- Many keep projects on GitHub mainly for free Windows/macOS runners; replicating that cross-platform CI elsewhere is costly in time and money.
- Some self-host with Forgejo and NixOS and report better performance than GitHub Actions, but admit setup and ongoing maintenance overhead.
- Commenters stress people underestimate the value of Microsoft paying for large amounts of CI for public repos; hobbyists in particular would have to reduce CI usage or pay real money elsewhere.
Self-hosting and alternative forges
- Alternatives mentioned: Forgejo, Codeberg, GitLab, Bitbucket, Sourcehut, Tangled, Radicle, GitSocial, v-it.org, gitnostr.
- Forgejo + self-hosted runners seen as viable for those willing to manage infra; Oracle’s free cloud tier is one example, but comes with delete-at-will risk.
- Sourcehut praised (especially email-based workflows) but lacks LFS; considered more demanding for contributors.
- Bitbucket criticized as slow and unreliable compared to GitHub.
- Some claim Codeberg is a “1:1 replacement”; others say its strong policies (e.g., against AI‑generated code, “vibecoding”) limit it as a general substitute.
Social features, discovery, and network effects
- Big divide: some heavily use GitHub’s stars, activity feeds, search, and fork network graph to discover and track projects; others almost never discover software via GitHub itself and rely on blogs/Reddit/HN.
- Network effects around accounts, low signup friction for issues/PRs, and name recognition are seen as GitHub’s hardest‑to‑replace advantages.
- Several want federated social features (stars, activity, forks) so they can leave without losing that graph.
Decentralization and federation efforts
- Forgejo and ForgeFed, plus ActivityPub-based federation (including federated starring) are cited as emerging directions.
- Radicle is praised for modeling issues/PRs and identities as git objects, making repos self-contained and more naturally federated; still seen as experimental and lacking mature CI.
Version control and philosophy
- Long subthread clarifies confusion between Git and GitHub: Git is decentralized VCS; GitHub is a centralized forge built on it.
- Debates over Git vs SVN/Mercurial: Git is harder to reason about but offers cheap branching and powerful merging; SVN’s model was simpler but less capable.
Private/closed-source and companies
- For small companies, arguments for GitHub: convenience, integrated issues/CI/hosting, lack of IT staff, and internal bureaucracy around hosting servers.
- Counterpoint: if code is a core asset, self-hosting ensures control, backups, and independence from a third-party changing terms or failing.
Reliability, ethics, and UX
- Some want to leave GitHub over reliability issues and outages; others see ethical boycotts as overblown compared to “worse companies” elsewhere.
- One user left because GitHub’s modern UI blocks NoScript/basic HTML use.
- GitHub is described as two products: a social OSS platform (hard to replace, mostly read-only use) and a team tool (where UX, notifications, and PR/issue workflows often feel painful and “corporate”).
- GitLab is criticized as even more corporate-feeling and weaker on discovery, though feature-complete for many use cases.