811–820 of 952 posts
Earlier quoted context omitted.
Feeling empathy for their pathetic fragile existence doesn't mean you sympathise with said fragility.
Not being able to control your anger issues and name calling ppl as a public face of your org sounds pretty fragile to me.
So much vague outrage over nothing. That CI system created by so called monkeys is the one of the best free CI service in the world. Not everyone has the millions of dollars like Zig Foundation to create their own CI servers. After that they appreciate GitHub Sponsors, but say it is now a complete liability just because a project leader left. What are the actual changes? Any new rule? But no, it is now a "liability"…
Anyone who has ever used Gitlab, or dare my foul mouth say Jenkins, has experienced a better system than Github actions. Unless it's miraculously improved recently as it's been a couple years for me, they didn't even document their regex/pattern matching. Best I could find via searching was that it was whatever Ruby used, which wasn't any kind of real standard. I don't want to call anyone names, but whoever defends s…
Earlier quoted context omitted.
It means to be snidely controversial. > Putting aside GitHub’s relationship with ICE… If you actual actually wanted to put that aside, you could have…put it aside. (Plus it being weird on a substantive basis. Selectively blacklisting specific government agencies…that’s just not a sustainable approach.)
What's unsustainable about it?
Every service has rules but are the rules clear and consistent enough that organizations can reliably use the service without worrying they’ll be terminated.
Earlier quoted context omitted.
Brb founding a SaaS startup. I’ll call it cloudsleep dot io of course. After our Series B I’ll buy the .com. Only task to do before lining up investors is how can I weave AI into our product?
Describe the task you're waiting for as text, and let an LLM pick the number of seconds for each request. More expensive the better model you clearly need for this. There, your AI pitch.
> 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…
I thought people knew andrewk was an ahole? I thought that was his supposed charm? Like Linus. I mean https://github.com/ziglang/zig/pull/24317 wasn't that long ago.
The arguments seem... really weak ? They just linked to some random obscure bug and an obscure OS not being supported in containers (and I'd imagine solution being "just bring your own runner"). I have... questions about Zig leadership
> obscure OS not being supported Believe it or not, there are platforms outside of the big 3. The GitHub Actions runner does not work on FreeBSD, NetBSD, OpenBSD, and illumos, all of which are operating systems we either have existing support for, or intend to start supporting properly soon. (We already have FreeBSD CI; machines for the other 3 are arriving at my place tomorrow as it happens.) And that's ignoring CPU…
That's great. I hope it works out, and you have CI for NetBSD, OpenBSD, and illumos, too.
Go's support for NetBSD has been a big boon to the more casual NetBSD user who isn't going to maintain a port. It means a random Go open-source project you use probably works on NetBSD already, or if it doesn't, it can be fixed upstream. Maybe Zig could play a similar role.
It's a shame GitHub doesn't have native CI even for FreeBSD on x86-64. I can see the economic case against it, of course. That said, the third-party Cross-Platform GitHub Action (https://github.com/cross-platform-actions/action) has made Free/Net/OpenBSD CI practical for me. I have used it in many projects. The developer is currently working on OmniOS support in https://github.com/cross-platform-actions/omnios-builder.
Earlier quoted context omitted.
What is?
The question under discussion is 'open source developers posting childish rants vs not posting them' Not 'open source developers posting childish rants vs no open source developers'
they’d be hacking on shit over at Mozilla (or similar - likely for more money) right?
Earlier quoted context omitted.
What's unsustainable about it?
I thought this was obvious, but you will be asked to evaluate every government/organization on their morales. So they enforce immigration laws, not enforce it, enforce improperly, do they support abortion, do they support the right side in the Middle East, do they have racist policies, do they not have anti-racist policies, do they limit freedom of speech, do they not limit free speech enough. Every service has rules…
So what? Obviously you won't respond to all the permutations, so can draw only some red lines.
> without worrying they’ll be terminated
Yes, you can have some principles without increasing these concerns
Earlier quoted context omitted.
> obscure OS not being supported Believe it or not, there are platforms outside of the big 3. The GitHub Actions runner does not work on FreeBSD, NetBSD, OpenBSD, and illumos, all of which are operating systems we either have existing support for, or intend to start supporting properly soon. (We already have FreeBSD CI; machines for the other 3 are arriving at my place tomorrow as it happens.) And that's ignoring CPU…
> We already have FreeBSD CI; machines for the other 3 are arriving at my place tomorrow as it happens. That's great. I hope it works out, and you have CI for NetBSD, OpenBSD, and illumos, too. Go's support for NetBSD has been a big boon to the more casual NetBSD user who isn't going to maintain a port. It means a random Go open-source project you use probably works on NetBSD already, or if it doesn't, it can be fixe…
In fact, we do already have cross-compilation support for NetBSD (and FreeBSD). But we currently only "test" NetBSD by building the language behavior tests and standard library tests for it on Linux, i.e. we don't actually run them, nor do we build the compiler itself for NetBSD. Native CI machines will allow us to fill that gap.
As it happens, Go's cross-compilation support does indeed make our lives easier for provisioning CI machines since we can build the Forgejo Runner for all of them from one machine: https://codeberg.org/ziglang/runner/releases/tag/v12.0.0