GitHub Is Sinking: What's Wrong and Where to Go

Remember when GitHub was synonymous with "decent open source"? Now it feels like a leaky boat that Copilot and Actions are trying to patch, but the water keeps rising.

The article's author complains: the interface lags, search returns gibberish, issues and PRs take ages to load, and notifications arrive an hour late. Sounds familiar, right? Especially when you're waiting for a critical fix approval and GitHub decides to "think about it" for a while.

And it's not just about speed. Stars vanish, repositories get deleted without explanation, and support replies with templates. Looks like Microsoft figured that with monopoly comes the luxury of slacking off.

What to do?

• Consider alternatives: GitLab, SourceHut, Codeberg.
• Don't keep your only repo copy on GitHub — use mirrors.
• For commercial projects, think about self-hosting.

GitHub isn't fully underwater yet, but the holes in the hull are getting bigger. Maybe it's time to hop on a lifeboat?

METABYTE studio's take: We've noticed GitHub sometimes ponders pull requests longer than our devs ponder code. If you want stability — come to us, our CI/CD runs faster than your internet on a Friday night.