>>23385 (OP)
>where does the slack get picked up if not by SystemD? Daemons?
yeah, just other software that does the same job. not all of is is shit that needs to be present 24/7 though, or even present at all.
>Arch users end up trying Artix, but complain that some stuff didn't work, and that they're better off at that time using Arch.
I call bullshit. A couple things haven't worked for me, but they were:
1. Programs I didn't want to auto start trying to make themselves auto start without asking me. Obviously that not working is a feature and not a bug.
2. One of my drivers had a regression and one of the workarounds involved installing semi-obsolete software that was reliant on systemd. There actually had been an openrc version made, and it had been available on artix repos, but it was no longer maintained and was no longer available. I probably could've figured out how to do the conversion myself, but I found a different workaround instead that works better anyways
I did install one of the community editions, so I suppose they probably installed the base iso and got mad when the initial setup differed.
>Why is SystemD a poor choice compared to the competition, is it really so bad?
Honestly it's not that bad, but there's some parts of it I fucking hate having to deal with, whereas I have never found myself getting mad at openrc or sysvinit. so it's not even that systemd is unfathomably evil, it's that you can't make me pick my 5th choice when the other 4 choices i prefer over it are still there and viable.