Here’s something that’s both surprising and, in a way, not surprising at all, especially after yesterday’s announcement from KaOS, a distribution long known for its deep commitment to the KDE Plasma desktop, that it plans to move away from it. The main reason cited was KDE’s reliance on systemd in a specific component.

As expected, the news quickly gained traction, prompting KDE to clarify its dependence on systemd and which parts of the desktop environment rely on it. In a post on KDE’s Reddit community titled “A quick anti-FUD FAQ to debunk ‘the KDE is forcing systemd!’ hoax“, the contributor described the claims as misinformation and provided a short FAQ clarifying the project’s position.

  • bestboyfriendintheworld@sh.itjust.works
    link
    fedilink
    arrow-up
    3
    ·
    3 hours ago

    Systemd ist great and people who hate it, are also likely the same ones running openbox or a similar ancient window manager.

    KDE should do what enables best user experience, not bend over for radicals stuck in the past.

    I think KDE should force systemd.

  • exu@feditown.com
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    3
    ·
    15 hours ago

    The truth is nobody is building an alternative to a bunch of great API that systemd just gives you for free.

    • kbal@fedia.io
      link
      fedilink
      arrow-up
      11
      arrow-down
      15
      ·
      13 hours ago

      There isn’t “an alternative” to systemd because nobody who hasn’t drunk the kool-aid believes that anything like it should exist. The syslog, the cron daemon, the dns config, the log rotation, the ntp server, and even the init system should not all be part of one giant tangled mess of a project.

        • kbal@fedia.io
          link
          fedilink
          arrow-up
          6
          arrow-down
          2
          ·
          13 hours ago

          In that case there are alternatives for each component, most often more than one, though they may lack here and there some feature you believe to be indispensable.

  • mmmm@sopuli.xyz
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    16 hours ago

    I still wonder if the systemd imposition on the new login manager is absolute and can’t be circumvented in any way, i.e. GNOME is allegedly dependent on systemd but you can circumvent it by using logind instead of the full systemd install

    • nyan@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      8
      ·
      11 hours ago

      That’s because someone took the time to pull out the minimum required interface code from systemd to make elogind after gnome made such a mess of things. It’s a band-aid. More band-aids will no doubt be created to deal with this. It’s just that the necessity is annoying.

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    11
    arrow-down
    6
    ·
    18 hours ago

    I like how the “FAQ” answers questions nobody was asking and accuses opponents of truth, freedom, and systemd of “decontextualising comments on merge requests” without mentioning what was actually said by whom in those merge requests so we could judge for ourselves. As a PR move to put out the flame war (which itself does seem really pointless) it seems counterproductive. But it looks like it’s just another reddit post, not an official KDE policy statement or anything.