Live data from Hacker News

Migrating the main Zig repository from GitHub to Codeberg

ziglang.org

651–660 of 952 posts

Re: Migrating the main Zig repository from GitHub to Codeberg

#651
post #408

Earlier quoted context omitted.

I would agree if they weren't so clearly deserved. Calling shit out as being shit is fine.

Just because you think something is shit does not mean it becomes gospel for the rest of us. Millions of other people are fine with GitHub, respect their choice.

He didn't insult the people who are still using github.

Re: Migrating the main Zig repository from GitHub to Codeberg

#652
post #624

Earlier quoted context omitted.

I've seen this in other places as well. The bottleneck is not coding or creating a PR, the bottleneck is the review.

This ought to be automated using AI. It could first judge whether the PR is frivolous, then try to review it, then flag a human if necessary. The problem is that Github, or whatever system hosts the process, should actively prevent projects from being DDOS-ed with PR reviews since using AI costs real money.

> This ought to be automated using AI.

When the world is telling you to fucking stop, maybe take a moment and listen.

Re: Migrating the main Zig repository from GitHub to Codeberg

#653

Very questionable decision. You're running what aims to be a major programming language - have it where people expect and live with your gripes about the platform. In retail you set up your store in the biggest mall with the most customers walking past - sure you can go set up in some back alley but don't expect customers to come to your store. This remains true even if the mall owns forget to mop the floor. This fee…

> You're running what aims to be a major programming language - have it where people expect and live with your gripes about the platform. The core types who will make use of, contribute to, and/or otherwise use the repo likely don't need it to be on GitHub. Having it "where people expect" is useful for drive-by contributions but Zig doesn't really need that. Furthermore, why should we as a larger community cede thing…

[deleted]

Re: Migrating the main Zig repository from GitHub to Codeberg

#654

I'm happy to see the move. Codeberg is probably a more stable/long-term solution than SourceHut as the founder is slightly unhinged (but love what he has built). Honestly, either would have been great choices. More opensource projects should move off GitHub. I moved off it myself.

I am getting fatigued by all of these. I am learning about a new one each time. We have

  - GitHub
  - BinCode
  - GitLab
  - SourceHut
  - CodeBerg
They all seem to do roughly the same things, but with a different web UI. Competition is great! Especially in response to a big corp that has market share. But... there was value in the centralization of GH.

Re: Migrating the main Zig repository from GitHub to Codeberg

#655
post #69

Damn - Codeberg is snappy! It's as fast as Github used to be 10 years ago. Server rendered pages. No AJAX-style slow updates. Love it.

This was the very first thing I noticed when we (the Zig team) started seriously trialing Codeberg. Honestly, the transition was worth it just for the ability to navigate the website without a 3-5 second wait every time I click a link.

Codeberg performance is not good today - 12 seconds per click before any update. Not sure if they're able to scale.

Re: Migrating the main Zig repository from GitHub to Codeberg

#656
post #35

> As a bonus, we look forward to fewer violations (exhibit A, B, C) of our strict no LLM / no AI policy, Hilarious how the offender on "exhibit A" [1] is the same one from the other post that made the frontpage a couple of days ago [2]. [1] https://github.com/ziglang/zig/issues/25974 [2] https://news.ycombinator.com/item?id=46039274

oh god... he has a humongous AI generated PR for julia too https://github.com/tshort/StaticCompiler.jl/pull/180

The people of Jonestown collectively drank less kool-aid than all this.

I don't know whether to be worried or impressed.

Re: Migrating the main Zig repository from GitHub to Codeberg

#657
post #649

Earlier quoted context omitted.

This ought to be automated using AI. It could first judge whether the PR is frivolous, then try to review it, then flag a human if necessary. The problem is that Github, or whatever system hosts the process, should actively prevent projects from being DDOS-ed with PR reviews since using AI costs real money.

I mean this with all sincerity, try doing this yourself. The established projects are resistant to YOLOing their projects and running them on complete LLM autopilot. You are proposing a completely different development style. Fork Ocaml to Oca-LLM and Julia to Jul-AI and see how it goes.

I'm not trying to say that this is now projects ought to work right now.

I do think this is where we are heading, though.

No, existing open source projects are not ready for this and likely won't ever be.

It will start in the corporate world and maybe already has.

Re: Migrating the main Zig repository from GitHub to Codeberg

#658
post #95

> it’s abundantly clear that the talented folks who used to work on the product have moved on to bigger and better things, with the remaining losers eager to inflict some kind of bloated, buggy JavaScript framework on us in the name of progress. > More importantly, Actions is created by monkeys This writing really does not reflect well on Zig. If you have technical issues with Github, fine: cite them. But leave ad ho…

Yea... Nail in the coffin on them for me.

Re: Migrating the main Zig repository from GitHub to Codeberg

#659

It's a pity that the GitHub repository is not mirrored, probably making downstreams broken. Good move anyway.

It's a simple `git remote set-url` to fix it, unless you are using some github proprietary API which is the kind of vendor lock-in they want to avoid.

Re: Migrating the main Zig repository from GitHub to Codeberg

#660
post #649

Earlier quoted context omitted.

I mean this with all sincerity, try doing this yourself. The established projects are resistant to YOLOing their projects and running them on complete LLM autopilot. You are proposing a completely different development style. Fork Ocaml to Oca-LLM and Julia to Jul-AI and see how it goes.

I'm not trying to say that this is now projects ought to work right now. I do think this is where we are heading, though. No, existing open source projects are not ready for this and likely won't ever be. It will start in the corporate world and maybe already has.

> This ought to be automated using AI.

...

> I'm not trying to say that this is now projects ought to work right now.

which is it?

Post reply on HN