• flying_sheep@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        7 months ago

        I literally haven’t run into a single one in the whole time Arch has been using it.

        (I installed Arch shortly before it switched to systemd and have been using it since without pause)

        • 0x4E4F@lemmy.dbzer0.comOP
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          7 months ago

          You must be running hardware not older than 4 or 5 years. Try running it on hardware 10+ years old.

      • throwwyacc@lemmynsfw.com
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        What are the systemd bugs that are so bad? I kinda get the bloated comment, but I don’t really mind when it serves its purpose

        • 0x4E4F@lemmy.dbzer0.comOP
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          7 months ago

          Closing handles on services that for god knows what reason, just hang. Also stopping and starting services again doesn’t always work as intended.

          • throwwyacc@lemmynsfw.com
            link
            fedilink
            arrow-up
            2
            ·
            7 months ago

            That’s interesting. I’ve never had any issues with systemd directly mainly with poorly setup default configs I’m a big fan of a centralised place to manage services. Works super well with podman quadlets

            But I’m not too invested use whatever works for you I reckon

            • 0x4E4F@lemmy.dbzer0.comOP
              link
              fedilink
              arrow-up
              1
              ·
              7 months ago

              I’m also a fan of centralized places to handle things (I prefer having just one package manager, not the package manager and flatpak and pip and god knows what else), but there are other init/service managers.