I don't miss anything from the dark days of managing self-hosted CI servers.
Migrating the main Zig repository from GitHub to Codeberg
201–210 of 952 posts
Re: Migrating the main Zig repository from GitHub to Codeberg
#202Earlier quoted context omitted.
> I simply don't trust any decision these people make Do you have an example or two of poor decisions that push you away so strongly?
Clearly, my distrust is based on Andrew's publicly displayed character, not an analysis of historical behavior. When you see a Chef not wash his hands after using a restroom, you should avoid eating at their restaurant, even if you have no proof they don't wash their hands in the kitchen prior to cooking. The important observation for me is that he didn't know where to draw the line, and this is regarding people he d…
FWIW I've never programmed a line of code in zig and I don't know who this developer is.
All I got from it was "seems like GitHub is starting to deteriorate pretty hard and this guy's fed up and moving his project and leaving some snark behind".
Re: Migrating the main Zig repository from GitHub to Codeberg
#203Earlier quoted context omitted.
Not wanting to review and maintain code that someone didn't even bother to write themselves is childish?
Denying code not on it's merits but it's source is childish.
The vast majority of of LLM generated code that gets submitted in PRs on public GitHub projects is not that - see the examples they gave.
Reviewing all of that code on its merits alone in order to dismiss it would take an inordinate amount of time and effort that would be much better spent improving the project. The alternative is a blanket LLM generated code ban, which is a lot less effort to enforce because it doesn't involve needing to read piles and piles of nonsense.
Re: Migrating the main Zig repository from GitHub to Codeberg
#204Re: Migrating the main Zig repository from GitHub to Codeberg
#205Re: Migrating the main Zig repository from GitHub to Codeberg
#206Very 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…
Eh. Their messaging is immature here, but you don't need to be on the biggest thing - especially when you have a limited set of contributiors, not millions. It is deeply unfortunate that Git won instead of Mercurial and even more unfortunate that GitHub won. GitHub's code review/PR UI is an abomination. We had better tools 15 years ago and GitHub is still a regression. There are tons of reasons to move off it if you'…
Re: Migrating the main Zig repository from GitHub to Codeberg
#207> 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…
> created by monkeys I don't particularly care for either Zig or Github, but... they do precisely cite the technical issues. That snippet links to a Github discussion comment https://github.com/actions/runner/issues/3792#issuecomment-3... (reproduced below) "The bug in this "safe sleep" script is obvious from looking at it: if the process is not scheduled for the one-second interval in which the loop would return (du…
Where do you draw the line, then? Is a racist screed acceptable to you as long as the following paragraph references technical issues correctly?
The language in the blog post is insulting. Imagine how you would feel if you were the person who wrote this code, and now you are being called a monkey in front of thousands of people on the internet. Certainly you've made mistakes in your code before...or are you saying you've always written flawless code without errors?
These codes of conduct always seemed a bit superfluous to me, but after reading comments like these I can totally see why they are necessary.
Re: Migrating the main Zig repository from GitHub to Codeberg
#208https://www.ice.gov/news/releases/top-story-industry-partner...
There is a purity spiral that organizations can enter when they start doing this, which ends up with you shoving yourself into a cold dark corner of the internet and still not being completely detached from the badness because Cisco provides infrastructure for nearly every major weapons manufacturer and defense department globally.
Re: Migrating the main Zig repository from GitHub to Codeberg
#209> 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…
> created by monkeys I don't particularly care for either Zig or Github, but... they do precisely cite the technical issues. That snippet links to a Github discussion comment https://github.com/actions/runner/issues/3792#issuecomment-3... (reproduced below) "The bug in this "safe sleep" script is obvious from looking at it: if the process is not scheduled for the one-second interval in which the loop would return (du…
Re: Migrating the main Zig repository from GitHub to Codeberg
#210Earlier quoted context omitted.
I must be missing something huge here, or maybe it's the wine -- how is the code in PR 3157 (referenced in a later comment) a proper fix? https://github.com/actions/runner/pull/3157/files Is : doing something unusual in GH actions?
The original loop is: while (time() != timeout) {;} The fixed loop is: while (time() < timeout) {;}