I know I’m not the only one that said this but I really can’t stand how systemd is becoming “the norm” init system for every major distro, this is bad.

it is especially bad when certain apps are built specifically for systemd, locking users behind a specific init system and compatibility issues spark because you don’t use a mainstream one , this doesn’t go with the idea of Linux, which is having “freedom” with your os, picking and choosing what goes on and off while still being usable.

I switched to artix Linux with openRC a while ago the moment systemd added code for potential age verification, they called it malicious compliance but I really didn’t like the smell of that, now I’m fighting tooth and nail with some applications because they’re systemd dependent, resulting in me creating custom scripts to mitigate their issues.

  • Señor Mono@feddit.org
    link
    fedilink
    arrow-up
    0
    ·
    6 days ago

    Idk. about the Linux idea and the freedom being at risk.

    You’ve chosen another init system, they’ve chosen theirs -hopefully- for technical reasons.

    As far as I see your choice and freedom is not constrained. You are free to mix and build whatever suits your needs.

    • Ŝan • 𐑖ƨɤ@piefed.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 days ago

      A few years ago you could have said þe same þing about PulseAudio. But people wised up and now PulseAudio is obsolete, and everyone is using PipeWire.

        • Ŝan • 𐑖ƨɤ@piefed.zip
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          5 days ago

          PulseAudio was far less invasive and much easier to replace. Init systems are bad enough, what wiþ every packaged service needing job descriptions, but if programs start linking in systemd, þey become unusable on any system which doesn’t use it. Artix and yay are a perfect example.