Evaluating new software forges

Original Article ↗ Hacker News Discussion ↗

Developers weighing alternatives to GitHub are grappling with trade-offs between convenience, control, and philosophy around issues like AI training, open-core licensing, and centralization. Commenters compare mainstream forges (GitHub, GitLab) with self-hosted options (Gitea/Forgejo, SourceHut, OneDev, Radicle and other Web3-style platforms), highlighting differences in CI tooling, maintenance burden, federation efforts, and community-building. Many see mirroring code to GitHub for discoverability while hosting primary repos elsewhere as a pragmatic compromise, even as they criticize opaque policies, growing bloat, and opinionated governance on various platforms.

Landscape of Software Forges & New Options

  • Besides the major forges (GitHub, GitLab, SourceHut, Gitea/Forgejo, Codeberg, Bitbucket), commenters mention newer or niche options:
    • Radicle, protocol.land, Gitopia (all with Web3/crypto aspects to varying degrees).
    • Pierre for product-focused workflows.
    • OneDev, Ayllu, Fossil, Gitolite/GitWeb, darcs, Pijul.
  • Some see Radicle and similar projects as genuinely “new and exciting”; others are wary of Web3/crypto associations.

Self‑Hosting vs SaaS

  • Many are moving to self-hosted Gitea/Forgejo, GitLab, darcs etc., especially for low‑collaboration personal projects.
  • GitLab is viewed as feature-rich but heavy and maintenance-intensive; experiences range from “painful beast” to “rock solid with cron-based upgrades.”
  • Gitea/Forgejo are praised for simplicity; built‑in CI and Actions are maturing.
  • Some are experimenting with small independent hosting providers and “small web” ideals.

CI and YAML Workflows

  • Debate over “complicated YAML” in CI:
    • Some argue all modern CI (GitHub Actions, GitLab CI, SourceHut, Drone) effectively use similar YAML, so criticizing one and accepting another is inconsistent.
    • Best practice suggested: keep YAML thin and call scripts inside the repo to keep CI reproducible locally.

Email vs Web Workflows (SourceHut, Community)

  • Email-based workflows polarize:
    • Fans say they’re simple and tooling is the real problem.
    • Critics call them archaic, off-putting to “21st century” contributors, and bad for building broader communities.
  • Concerns about SourceHut:
    • Perceived hostility to pseudonyms vs clarifications that stable emails, not legal names, are required.
    • Policy banning most cryptocurrency projects raises questions about platform “freedom,” but others appreciate its explicit values and human review.

AI, Copilot, and Code Privacy

  • Strong concern about “AI-powered” forges training on hosted code, especially GPL/FOSS.
  • Some argue LLMs and Copilot are just tools and optional; others want their code entirely unreachable by AI, likening it to preferring “chef-made” vs industrial food.
  • Mirroring self-hosted repos to GitHub for discoverability while objecting to Copilot is called out as ideologically inconsistent by some.

Decentralization, Federation, and Discovery

  • Interest in:
    • ActivityPub/ForgeFed for cross-forge issues/PRs without accounts everywhere.
    • Federated search and opt‑in discovery instead of centralized GitHub dominance.
  • Several note it’s hard to build community if not on GitHub, but want discovery decoupled from hosting.

UX, Policies, and “Enshittification”

  • Complaints that GitHub’s React-based UI feels slower and jankier than before.
  • Worries about “enshittification” as forges chase vague AI trends.
  • Some see the blog author’s criteria and tone as inconsistent or overly caustic; others defend strongly opinionated personal writeups as still useful.