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?
  • @Fryboyter@discuss.tchncs.de
    link
    fedilink
    English
    131 year ago

    Is the current SystemD rant derived from years ago (while they’ve improved a lot)?

    In my experience, the same arguments against systemd (not systemD) are still used. No matter how often they have been disproved or whether the problem has been fixed in the meantime. With many users I am sure that it is only about making the project systemd bad.

    Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?

    I would prefer it if there were no rants at all. No matter what the topic. Because that doesn’t help in any way. It would make more sense to invest the energy in the projects in question or in alternative projects to improve them.

    • @taladar@sh.itjust.works
      link
      fedilink
      English
      11 year ago

      I would prefer it if there were no rants at all. No matter what the topic.

      I think it depends. A rant can be good if it is full of factual, demonstrated details about something that needs to be fixed. It is not so great if it just someone emotionally unloading about subjective preferences not going the way they want.