71
KDE Responds to FUD Over Alleged systemd Mandate (linuxiac.com)
submitted 8 months ago by to c/linux@programming.dev
33 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[+] -7 points 8 months ago (14 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 14 points 8 months ago (7 children)

    The Linux kernel is a tangled mess and not an alternative to the well designed HURD micro kernel.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 5 points 8 months ago (2 children)

    Both compile slower than the entirety of Plan 9.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 8 months ago (3 children)

    Like many, back when it was fashionable I was open to the possibility of that idea being correct and I guess it's still best to keep an open mind, but the results thus far suggest otherwise. Using Hurd is somewhat difficult for most purposes. Using cron rather than systemd timers on the other hand is much more pleasant and easy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 8 months ago (2 children)

    macOS runs on the Mach/xnu micro kernel and is pretty successful with it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 8 months ago (1 child)

    Apparently there have been attempts to make a free OS based on Apple's kernel, but wikipedia mostly talks about them in the past tense. Too bad, it would've been good to have such an option.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 8 months ago

    Pure Darwin ist still around.

    I tried out a Darwin distribution a few years ago. It was a BSD with some apple flavor. None of the GUI was included, not all drivers, firmware, etc.

    The community is tiny. There was also little incentive to try and fix things or add features, because upstream Apple ignored it pretty much. Grabbing the sources and compiling them into an operating system has little documentation from Apple.

    Mac OS X used to install XQuartz, a hardware accelerated Xorg/X11 server by default in the 2000s, but dropped it at some point.

    Even back when OpenDarwin and such were around, people would rather install YellowDog Linux that supported PowerPC Macs.

    I think at some point the old NeXtStep/OpenStep folks left Apple and the new engineers didn’t understand Unix or think it’s important.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 8 months ago (3 children)

    Then make a better alternative. You obviously "haven't drunk the koolaid".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 8 months ago (2 children)

    Not every Linux user casually writes init systems. Not every Linux user is a programmer, even. Even less have competence at promoting their project so that it would be meaningfully adopted.

    "Be the change you want to see" is cool and all, but Linux userbase can have opinions.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 8 months ago (1 child)

    "Write the code I want, free of charge, in your own time. I demand it. Recognition for your efforts? Nah, I won't even know of you, but if anything ever goes wrong, I will find your repo and complain about how Microslop did it better with hundreds of engineers!"

    That's what you sound like. If you don't contribute code, money, documentation, detailed bug reports, community guidance, moderating, etc., then IMO, that opinion is worthless.

    Devs aren't your code monkeys, shackled to computers to do your bidding. A lot of thankless, unpaid time went into writing most of opensource code out there. To sit there and demand options is, to me, appallingly ignorant behaviour.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 8 months ago

    I contributed money, translations and properly filed bug reports to various open-source projects. But I don't think people who don't shouldn't speak out. Being unhappy with a certain change signals the direction for the devs to make their code better.

    Besides, KDE is no hobby project; it's a nonprofit with full-time workers on a wage. Nonprofits are always kept to a high standard of accountability, and are resilient enough to turn negative feedback into directions for growth. It is in part this feedback that led it to develop the best DE out there.

  • permalink
  • fedilink
  • source
  • parent