Alexia Mar 13
Systemd has denied to revise their policy in regards to AI.

they've also marked evidence that people gave regarding its effectiveness as off-topic, then locked the conversation.

I believe the authors have not understood the weight of the issue. Later this day, I will begin drafting an open letter to Systemd's authors under the Starlight Network umbrella of projects. EDIT: or perhaps I will take a different approach. There's many more issues I want to talk about.
Disallow usage of generative AI to write code · Issue #41085 · systemd/systemd

Component No response Is your feature request related to a problem? Please describe Generative AI is actively killing people, driving up costs, and plagiarizing work from many open source developer...

GitHub
Show threadNerdNextDoor Mar 13
@alexia completely fucking ridiculous. at this point, we’d all be better off just recreating everything that AI has infected instead of arguing with these people.
Show threadAlexia Mar 13
@mrmasterkeyboard easier said than done, even just getting a hard-fork off of the ground is quite difficult, letalone a drop-in replacement
Show threadsarah tonin Mar 13

@alexia @mrmasterkeyboard i mean there's already openrc and s6 and the rest of systemd can be replaced with extra independant components on the side

putting everything in one place is exactly how we got into this mess, why recreate it ?

Show threadNerdNextDoor Mar 13
@SRAZKVT @alexia Just because you can recreate it doesn't mean you need to make the same choices as them too. That's the fun part of recreating things.
Show threadsarah tonin Mar 13

@mrmasterkeyboard @alexia the problem is the very design of a lot of systemd components is that each depend on several others in an incomprehensible web, so unless you're willing to cut some features, you'll need to redo the whole thing in mostly the same way

if you're fine with just a subset though, you should be mostly fine, but again, it'd be a subset, not 100% compatible

Show threadSIN001E/R-SINE | ΘΔ🦈 | 🏳‍⚧Mar 14

@SRAZKVT @mrmasterkeyboard @alexia i don't think you even really need to recreate systemd in the first place though

like, i've been running runit for a while now, and have had practically zero issues; turns out the vast majority of things that "depend on" systemd literally just need their service file rewritten, which in most cases takes 5 minutes

and on a distro built around runit like Void, that's of course already done in packaging

Show threadsarah tonin Mar 14
@sinewave @mrmasterkeyboard @alexia i don't think runit is perfect (even though i run it as well, and have for 4 years now), because runit doesn't handle service dependencies, but still, s6 and openrc exist and both support those
Show threadSIN001E/R-SINE | ΘΔ🦈 | 🏳‍⚧

@SRAZKVT @mrmasterkeyboard @alexia true, although there's a very simple (and very runit-y) solution; you just run sv check dependency and exit with nonzero if it fails

the overhead isn't particularly high since it waits a few seconds between attempts; and as it turns out not that many services even need explicit dependency handling

Mar 14 at 6:54amWeb