Jeff Bruchado
Back to blog

Zig Software Foundation Leaves GitHub: Microsoft Criticism and the Future of Open Source

Hello HaWkers, a controversial decision is generating intense debates in the development community. The Zig Software Foundation announced it is leaving GitHub, citing Microsoft's lack of attention to fixing critical bugs on the platform.

Have you ever stopped to think about the dependency the open source community has on GitHub? This move raises important questions about sovereignty and diversity in the development ecosystem.

What Happened

The Zig Software Foundation, the organization behind the Zig programming language, published a statement detailing the reasons for leaving GitHub. The decision comes after months of frustrations with unresolved bugs that directly affect project development.

Cited Problems

Ignored Bugs:

  • Critical issues open for more than 2 years
  • CI/CD problems affecting releases
  • GitHub Actions bugs with no fix timeline
  • PR interface with usability problems

Lack of Communication:

  • Tickets without response from the GitHub team
  • No effective channel for open source projects
  • Unfulfilled promises of fixes

Questionable Priorities:

  • New features being launched while basic bugs persist
  • Focus on enterprise features at the expense of community
  • Feeling that open source is not a priority

Who is the Zig Software Foundation

Zig is a systems programming language that has been gaining significant attention:

Language Characteristics

Proposal:

  • Modern alternative to C
  • Focus on simplicity and performance
  • Interoperability with existing C code
  • Zero-cost abstractions

Use Cases:

  • Operating systems
  • Drivers and firmware
  • Games and engines
  • WebAssembly

Notable Projects:

  • Bun (JavaScript runtime) is written in Zig
  • Tigerbeetle (distributed database)
  • Mach Engine (game engine)

Importance to the Ecosystem

Zig represents a new generation of systems languages and has an engaged community. The decision to leave GitHub signals real frustration from maintainers of important projects.

Where Zig Is Going

The Foundation announced migration to its own infrastructure:

New Infrastructure

Code Hosting:

  • Own Git server with Forgejo (Gitea fork)
  • Hosted on Foundation infrastructure
  • Full control over the platform

CI/CD:

  • Own continuous integration system
  • Dedicated hardware for builds
  • Greater control over the pipeline

Community:

  • Own forums
  • Matrix/IRC for communication
  • Independent documentation

The Bigger Problem: GitHub Concentration

This case highlights a broader issue in the open source ecosystem:

Excessive Dependency

GitHub Numbers:

  • 100+ million developers
  • 400+ million repositories
  • 90%+ of relevant open source projects

Concentration Risks:

  • Single point of failure
  • Policies can change unilaterally
  • Bugs affect the entire ecosystem
  • Lack of competitive alternatives

History of Concerns

The open source community has expressed concerns before:

Microsoft Acquisition (2018):

  • Initial fear about GitHub direction
  • Promises to maintain neutrality
  • Criticism of forced integrations

Copilot Controversy:

  • Use of open source code to train AI
  • Unresolved licensing issues
  • Profit from community work

Unilateral Decisions:

  • Repository removal due to government pressure
  • Policy changes without consultation
  • Preference for enterprise clients

Alternatives to GitHub

For projects considering diversification:

Existing Platforms

GitLab:

  • Self-hosted or cloud
  • Robust integrated CI/CD
  • Open source option (Community Edition)

Codeberg:

  • Non-profit
  • Focused on open source
  • Based on Forgejo

SourceHut:

  • Minimalist
  • Focus on email-based workflow
  • No mandatory JavaScript

Gitea/Forgejo:

  • Self-hosted
  • Light and fast
  • Easy to maintain

Migration Considerations

If you're considering migrating your project:

Pros:

  • Independence from big tech
  • Control over infrastructure
  • Alignment with open source values

Cons:

  • Less visibility (network effect)
  • Fewer ready integrations
  • Maintenance cost
  • Community learning curve

What This Means For Developers

Important Lessons

1. Diversification is Prudent:
Even if you use GitHub, consider having mirrors on other platforms.

2. Self-hosting Has Value:
For critical projects, hosting your own infrastructure may make sense.

3. Community Matters:
Choose platforms aligned with your project's values.

Practical Actions

# Create mirror of your repository on another platform
# Example with Codeberg

# Add secondary remote
git remote add codeberg https://codeberg.org/user/project.git

# Push to both
git push origin main
git push codeberg main

# Automate with script
#!/bin/bash
git push origin main && git push codeberg main
# GitHub Actions to sync mirrors
name: Mirror to Codeberg

on:
  push:
    branches: [main]

jobs:
  mirror:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Push to Codeberg
        run: |
          git remote add mirror https://codeberg.org/user/project.git
          git push mirror --all --force

The Future of Open Source

This episode raises questions about the future:

Possible Trends

Decentralization:

  • More projects considering alternatives
  • Federation between platforms
  • Protocols like ForgeFed gaining traction

Pressure on GitHub:

  • Need to improve open source service
  • Risk of losing important projects
  • Community more vocal about problems

New Solutions:

  • Non-profit platforms growing
  • Software Forge Federation
  • Interoperability between platforms

Conclusion

The Zig Software Foundation's decision to leave GitHub is an important warning to the community. Excessive concentration on a single platform, controlled by a big tech company, creates risks we often ignore.

I'm not suggesting everyone abandon GitHub. The platform has merits and the network effect is real. But it's worth reflecting on diversification, having backups on other platforms, and supporting alternatives for a healthier ecosystem.

If you're interested in programming languages and the future of development, I recommend checking out another article: Anthropic Acquires Bun where you'll discover how Zig is connected to the JavaScript ecosystem.

Let's go! 🦅

💻 Master JavaScript for Real

The knowledge you gained in this article is just the beginning. There are techniques, patterns, and practices that transform beginner developers into sought-after professionals.

Invest in Your Future

I've prepared complete material for you to master JavaScript:

Payment options:

  • 1x of $4.90 no interest
  • or $4.90 at sight

📖 View Complete Content

Comments (0)

This article has no comments yet 😢. Be the first! 🚀🦅

Add comments