Live data from Hacker News

Bye, Bye GitHub

log.ozgur.works

41–50 of 80 posts

Re: Bye, Bye GitHub

#41
Btw, did anyone notice they removed access to "who starred the project" recently. You can only check your own repos, not external ones. It was very nice to find related people before.

Re: Bye, Bye GitHub

#43
I'm in the middle of a Forgejo migration myself for similar reasons. What finally pushed me over the edge was a hour long Actions outage that prevented me from pushing a hot fix for a bug to my webapp. (I relied on GH Actions to build and push an ARM Docker image.) For work that a business depends on, I can't recommend GitHub Actions. It's not just the outages that personally annoyed me, but the fact that I'm paying for it as well. So far I'm loving Forgejo and have no regrets!

Re: Bye, Bye GitHub

#44

GitHub is going the wrong way, but there really is nothing workable for open-source projects except GitHub. I don’t want to register on all these random GitHub killers just to open an issue or PR in a random project I’ve interacted with. For personal or team setups, any third-party service will work well.

> GitHub is going the wrong way, but there really is nothing workable for open-source projects except GitHub.

Open source projects existed just fine before GitHub, and they will exist just fine if they choose to move off GitHub as well. It's not a big deal if people won't do drive by contributions any more.

Re: Bye, Bye GitHub

#45

With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend. While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account. I might need to bite the bullet and go with GitHub. Regardless of what I th…

It ridiculous, Codeberg did the same. I get why, really, I do, but it's creating a severe damage that will be abused by a third evil actor that will take over the wasteland of GitHub and GitLab by creating a service that will allow anything (until it is enshittified of course)

Outcome? Everyone on their own self-hosted git servers, zero collaboration.

Re: Bye, Bye GitHub

#46

IME switching git providers is very hard, especially getting off of github. Most companies have insane numbers of integrations, automations, etc on top of GH. So yeah, its on us, but its also pretty simple algebra: does GH's downtime affect us more than the cost of switching? Most companies the answer is no. When people ask why people aren't switching to Gitlab, ADO, Bitbucket, etc, I believe this is the reason.

Most companies aren't on GH at all, but are doing some internally hosted forge. Companies who build on GH are very much in the minority in my experience.

Re: Bye, Bye GitHub

#47
post #45

With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend. While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account. I might need to bite the bullet and go with GitHub. Regardless of what I th…

It ridiculous, Codeberg did the same. I get why, really, I do, but it's creating a severe damage that will be abused by a third evil actor that will take over the wasteland of GitHub and GitLab by creating a service that will allow anything (until it is enshittified of course) Outcome? Everyone on their own self-hosted git servers, zero collaboration.

> Outcome? Everyone on their own self-hosted git servers, zero collaboration.

Everyone sticking to Github, then a year or two from now Github resolves their scaling issues and the competitors miss their window of opportunity to disrupt

Re: Bye, Bye GitHub

#48
post #27

The problem is nothing competes with GitHub. I know, GitLab. Gitea. Bitbucket. They have some features, but it’s like suggesting I drive a Nissan Sentra because my BMW breaks down once in a while.

My dude, that Nissan will get you from point A to point B just as effectively as a BMW will. Your analogy is working against you, not for you.

Re: Bye, Bye GitHub

#49
post #35
post #23

What frontier model did GitHub train? All of the frontier labs scraped GitHub like they scraped everything else. While GitHub has certainly tried to profit from AI, directing ire at GitHub for frontier labs training on public code seems misplaced.

Microsoft owns GitHub.

What frontier model did Microsoft train?

Re: Bye, Bye GitHub

#50

With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend. While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account. I might need to bite the bullet and go with GitHub. Regardless of what I th…

Oh my. I hadn't noticed this, but I've been kind of expecting it. I've been a big SourceHut user for years now. So I'll be having to decide what to do myself. I absolutely get their stance, but I don't see a world in which I will go back to writing meaningful amounts of code by hand again.

I may try out tangled.sh. It's really nice to have my code stored and backed up somewhere other than infra I control and manage.

Post reply on HN