103
GitHub faces a fight for its survival at Microsoft
(www.theverge.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 May 2026
103 points (100.0% liked)
Programming
27035 readers
166 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Codeberg is great, but let's not pretend that it's a replacement for GitHub. Notably they don't allow private repos and can't offer free CI (not in the same way as GitHub anyway). Plus, I don't see how they would be immune to the slopnami either if they became popular.
Best case would be if GitHub survives and just improves their reliability. I would not be surprised if they start imposing some kind of stricter limits on free accounts though.
I fundamentally disagree on your conclusion.
Codeberg is a non profit under German law. There won't be openai "non profit but not really" bullshit.
And your point about CI Integration ins good example: There is no "free" CI. GitHub lets you pay with their vendor lock-in and your data.
If that's okay with you, that's okay with me - but as a programming community as a whole ,especially FOSS side, this needs to go away.
The best case for me is that GitHub dies and its death is a wake-up call to decouple collaboration layers in a way that keeps them modular enough to not again rub into "too big or integrated to fail".
And yes, I'm aware that this is 2/3 day dreaming. But that's my best case association anyway :D
What vendor lock-in? GitHub barely has any.
That's fair it has loss leaders and network effects more so. The vendor lock in is non-git, non-ci side. So issues, orgs, etc. Actually you can see where they embraced opensource vs extending solely by the degree it is vendor locked.
If they stole it, it's a loss leader, if they made it, it's vendor locked.
Yeah I would say issues are minimal lock-in since they barely have any features (just labels I guess?) and can easily be exported. CI must be the biggest lock-in. If you have a complex CI system that makes use of lots of third party actions it could be a decent amount of work to migrate it. But not a huge amount.