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.

  • atzanteol@sh.itjust.worksEnglish
    3·
    10 hours ago

    you can swap bash for zsh or ls for busybox without breaking the whole system

    Is that so? rm -f /bin/bash and reboot. I’ll wait… Go ahead. You’ll be amazed at how many thing rely on bash. Or indeed sh which is why bash runs in bourne compatible mode when executed as /bin/sh.

    The idea of Linux isn’t just about running big software, it’s about the ability to compose a system from independent parts.

    This has never been true. The Linux kernel team themselves reject this silliness with a monolithic kernel that required a very specific toolchain to even build and run. Linux has always had tight integration.

    We’ve had many competing implementations of some things (desktop environments come to mind) but that is not the same as “build a system out of Lego components” as a design goal. It’s what you get when you have no direction. It would be a very stupid design goal.