Linked by jessesmith on Wed 5th Nov 2014 10:39 UTC
Linux Over the past year I've been reading a lot of opinions on the new init technology, systemd. Some people think systemd is wonderful, the bee's knees. Others claim that systemd is broken by design. Some see systemd as a unifying force, a way to unite the majority of the Linux distributions. Others see systemd as a growing blob that is slowly becoming an overly large portion of the operating system. One thing that has surprised me a little is just how much people care about systemd, whether their opinion of the technology is good or bad. People in favour faithfully (and sometimes falsely) make wonderful claims about what systemd is and what it can supposedly do. Opponents claim systemd will divide the Linux community and drive many technical users to other operating systems. There is a lot of hype and surprisingly few people presenting facts.
Thread beginning with comment 599228
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Straight from the horse's mouth.

Essentially, it's about using libinput for input handling.
By making use of logind, they can improve security without needing to write and maintain yet another KDE-specific library.

Thanks for the quote proving my point ;-)

Essentially, libinput is needed to properly support Wayland; libinput requires a logind interface. Thereby Wayland requires logind.

However, KDE's (and likely Wayland's too from the description) integration is such that they don't care if it is logind or something else that provides the same D-Bus interface with respect to KDE on Wayland.

KDE on other systems (Xorg, Windows, BSDs, etc) is not affected. ;)

In otherwords, they did it right.

Reply Parent Score: 4