It's a real problem to run a project like Zig if your CI doesn't work. I guess we could have paid for an external CI service, but that as well would depend on GitHub APIs, so we would have gained what, a couple years? Given the current trajectory of GitHub I wouldn't trust them to maintain those APIs correctly for any longer than that (and as far as I know the current vibe-scheduling issues might already be reflected in the APIs that third party CI providers would use).
Let's not forget that "GitHub is an AI company now".
They won't get there tomorrow or the next month, but I'm sure there has been a time where people started moving from Sourceforge to GitHub and somebody else remarked that they were doing something needlessly risky.
As far as we can tell Codeberg is a serious attempt at a non-profit code sharing platform and we feel optimistic enough about its future that we're willing to bet on it.
> A better parallel would be not posting anymore on Hacker News anything Zig related, in terms of potential outcome.
I've been thinking about this lately and in my experience (having seen the effect of HN posts in the past when Zig was smaller vs now) the community is already big and vibrant enough that an HN post alone doesn't do too much of a difference. To be clear, I don't think that HN is losing relevance (unlike all the other big platforms mentioned earlier in this conversation), but our situation has changed.
People now are more and more learning about Zig though cool Zig projects, not by looking at yet another superficial language comparison blog post, which is the kind of content that tends to get to the top of HN more often than not.
More in general I think that your point about not pulling away from all the markeplaces of ideas is valid, but most of those marketplaces are not as good as they claim to be and we have the luxury to run a project that has a strong community connected to it, meaning that we won't be starved of attention or contributors by moving away from GitHub.
This whole situation has an interesting parallel with what's happening in our community wrt chat platforms, if we happen to be at the same tech event in person I'll be happy to share with you all the details :^)
You despise and are leaving GitHub, but intend to keep collecting money from their sponsorship feature/program? Sounds like they are doing something right then…
Using Namespace made it clear how much cruft GitHub Actions has accumulated and how much performance they leave on the table. I regard GitHub Actions like Nix: weird configuration, largely shell-based, and the value you get out is commensurate with the investment you put in. But it works well enough.
But at the end of the day, GitHub Actions, like Nix, is just shell scripts. They're fairly portable. I like Namespace because they fixed the parts of CI that matter, like fast local caching versus GitHub's HTTP-based cache.
But I also don't hate this: I use GitHub for the pretty website and global search. Someone will mirror Zig for the search, and my terminal does not care where I clone the repository from. I think this is the new world we live in.
Someone will have to build the aggregator that indexes all repositories and makes them searchable, but that can ultimately be separate from hosting.
Nah
I do think the combo of not using Twitter, not using Discord, and not using GitHub does make it a bit more challenging for Zig to become a mainstream programming language. Twitter being the least important amongst those. Hard to say how much it matters in practice, as things tend to win on their strengths and not on lack of weakness
k
Prospective Zig contributors can just adapt a bit and not care about the fact that the project isn't hosted on GitHub, then.
Right?
Another problem with that is that you know what you are leaving, but you don't really know what you find in the new place. GitHub used to go down often in the early days. Now they may not be snappy and unfortunately like 99% of the web felt for this Javascript framework craziness. But the site is always up, I bet has disaster recovery and serious backup policy, and so forth. Can you find this so obviously in other smaller places?