Yarmo writes on his blog:

My interpretation? The Microsoft Github ship is sinking and it’s sinking faster every day. The beauty is: you don’t need them.


I agree, you don’t need Github. In fact, you don’t need much of an infrastructure at all. That all being said, I don’t think Github is sinking per-se. Microsoft hasn’t even owned them for that long, and their recent purchase and integration of Node/NPM into the system ensures that they’re going to stick around for a bit.

I do, however, agree that hosting your code is something you can easily do on a wide variety of systems. I, personally, use Github. I do have all of my repositories backed up to my NAS, just in case. I’ve used Gitlab, and while they’re very good, I don’t need 80% of the features (same with Github). I used to have a self-hosted Gitea instance, but managing my own stuff became too much of a burden, especially on my anemic Raspberry Pi 3 (1gb).

Thankfully, there are a lot of hosts out there, as Yarmo points out:

selfhost your own Gitea instance if you have the knowledge;

use Codeberg.org which also uses Gitea;

use sourcehut.org which takes a different but very solid approach to git hosting;

use any instance generously hosted by amazing people (think libreho.st and Chatons);

use gitlab.com or selfhost an instance.


Git, being distributed in nature, allows you to host in all of those places, all at once. Pick and choose or just use one. Depends on what your personal needs are.

Github isn’t going away, it’s just getting the same kind of Microsoft hosted services administration that we’re seeing in Office 365: Lots of little blackouts and brownouts.