Because of the ubiquity, nay, monopoly of systemd I always assumed it was miles ahead of other init systems. Nope. I’ve been using a non-systemd environment for a while and must say I’m surprised by how little breaks, i.e., next to nothing. Moreover, boot and shutdown times are faster, and more of that good stuff. I suggest trying it out.

https://nosystemd.org/.

  • azimir@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    3
    ·
    2 hours ago

    Use what works for you.

    Develop what scratches your itch.

    Don’t tell OSS devs who are volunteering unpaid labor what they should do for you.

    If you want a solution that’s non-systemd go for it. If it doesn’t exist make it or pay someone to do so. Write from scratch or fork a project and get to work. That’s the way of the Bazaar.

    I’ll be in my unenlightened “things work for me good enough” Linux world using what works. Systemd is fine and rarely gives me problems. Actually, I’m not even sure I can remember any.

    Huge thank you’s to the devs who make this all possible. You rock!

    • greyscale@lemmy.grey.ooo
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      Its built antithetically to the unix principles, it uses binlogs, its slow and its a big ol’ bloated mess on low-memory embedded devices, and seemingly is creeping into the whole system.

      Also the original author has since fucked off to microslop so I don’t care what he thinks or does.

      It, as a project, also bent the fucking knee.

    • arsCynic@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      2 hours ago

      Use what works for you.

      True, but many don’t know other init systems might work for them because of the same wrong assumption I had.

      Huge thank you’s to the devs who make this all possible. You rock!

      Definitely. One big ecosystem with a multitude of developers working on a multitude of projects.