• N.E.P.T.R@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    2
    ·
    edit-2
    2 days ago

    My personal reasons for disliking systemd (note: I still use systemd):

    • The lead developer of systemd has said multiple times that we should be fine with break POSIX if it means developing faster.
    • systemd has massive attack surface, making it easier to exploit and result in privilege escalation. It is a highly complex and large codebase that really shouldnt be given the trust of PID 0
    • systemd is not portable or modular.
    • It only just barely got musl support. Hope to see it improve in the future.
    • systemd is much slower than other inits (eg. dinit, s6, openrc)
    • systemd being the go-to init encourages developers to more heavily depend on it, making it difficult for distros without systemd

    The biggest feature I like about systemd is run0, though I wish it was a drop in replacement for sudo. Secondly, I do like that services can be sandboxed.

    • nesc@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      4
      ·
      2 days ago
      • It’s developed for linux and there is literally 0 linux distributions that are POSIX-compliant, also standard is dead.
      • It doesn’t, also moving it to any other PID won’t make any difference.
      • It is modular (IIRC there is only three mandatory parts) and portable.
      • Was completely on musl side (also musl is as much not portable and modular as systemd 🙃 and in every practical way worse than glibc).
      • It’s not an init, nor does it present itself like this. Do you have any benchmarks that show this slowness when doing comparable operations?
      • Why exactly depending on a stable system component is a bad thing? Distros without systemd are moving against the stream, obviously there going to be some problems.
      • ferrule@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        4 hours ago

        For me the portability issue wasn’t really solved. I still work on embedded devices where I need to squeeze out every cycle and every byte of memory i can. Running systemd is an automatic no go, but in the *nix way of doing things I do have other options, so that’s good.

        But the more people depend on the systemd ecosystem rather than an open standard, the availability for me to use other projects goes down. Again there are usually options, but it’s sad to see no one really thought about that when everyone jumped on board.

        I also love the BSDs and other Unix systems. I remember decades ago downloading FreeBSD on my Gentoo box and was able to load the same Gnome desktop on both systems. Two totally different operating systems running the same UI. It sucks that targeting systemd might make software not run on other *nix operating systems

        • nesc@lemmy.cafe
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 minutes ago

          That’s pretty niche use-case devices that can run linux but at the same tume limited enough that systemd is the bottleneck. I do get it that running systemd on some embedded devices makes little sense.

          Systemd has stable API so nothing stops other systems from implementing parts of it that interest them, thing is, *bsds aren’t interested or resource constrained so much that they can’t.