• Allero@lemmy.today
    link
    fedilink
    arrow-up
    27
    arrow-down
    2
    ·
    14 hours ago

    I’d say the main bad part of systemd is how it’s used and now expected everywhere.

    If you search for some Linux guides or install something complicated or whatnot, they always expect you to have systemd. Otherwise, you’re on your own figuring how things work on your system.

    This shouldn’t really happen. Otherwise, yes, it’s great, it integrates neatly, and is least pain to use.

    • Strit@lemmy.linuxuserspace.show
      link
      fedilink
      arrow-up
      16
      ·
      12 hours ago

      In my opnion, systemd is like core-utils at this point.

      It’s so integrated into most things and the default so many places, that most guides assume you have it.

    • whaleross@lemmy.world
      link
      fedilink
      arrow-up
      15
      arrow-down
      1
      ·
      13 hours ago

      There is no authority delegating responsibilities of writing tutorials for Linux. It is the responsibility of nobody and everybody. If you can’t find one for your problem, write it yourself when you have figured it out.

      • Allero@lemmy.today
        link
        fedilink
        arrow-up
        8
        arrow-down
        2
        ·
        edit-2
        13 hours ago

        Sure, but I can’t single-handedly create an entire knowledge base on doing everything with X, so it’s a real and big limitation.

        • whaleross@lemmy.world
          link
          fedilink
          arrow-up
          8
          arrow-down
          4
          ·
          edit-2
          12 hours ago

          If you think so and that this is important, maybe you could be the one that makes it happen. Start a project and gather like-minded people. That is how Linux, FOSS and community driven efforts operate. It’s useless to complain that nobody else makes the effort if you have the capabilities but can’t be arsed making an attempt yourself.