SystemD is blamed for long boot times and being heavy and bloated on resources. I tried OpenRC and Runit on real hardware (Ryzen 5000-series laptop) for week each and saw only 1 second faster boot time.

I’m old enough to remember plymouth.service (graphical image) being the most slowest service on boot in Ubuntu 16.04 and 18.04. But I don’t see that as an issue anymore. I don’t have a graphical systemD boot on my Arch but I installed Fedora Sericea and it actually boots faster than my Arch despite the plymouth (or whatever they call it nowadays).

My 2 questions:

  1. Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
  2. Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
  • nottheengineer@feddit.de
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    As someone who recently started learning linux properly by setting up arch, systemd is nice. It does a lot of things that make life easier for me and it never gets in the way.

    Edit: Please disregard, this should be a top level comment.

    • Vilian
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      why did you ctrl c ctrl v your own comment?

      • nottheengineer@feddit.de
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Because it was intended to be a top level comment and I only noticed that I wasn’t commenting on top level after posting it.

        Did the deletion of this one not get through to your instance yet?

        • Vilian
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          oh, lol, it’s fine

          Did the deletion of this one not get through to your instance yet?

          probably

          • nottheengineer@feddit.de
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Alright, I thought I was quick enough but deletion seems to work differently in the federation. I restored the comment and added an edit, that should avoid confusion once everything is synced properly.