That's interesting. In the past, KDE has tried to make their software not dependent on linux functionality so that KDE can work in other places, like BSD and -- god help us -- Windows.
Since I only used KDE on linux, that's kind of frustrating. E.g. KDE refused to use FUSE (Filesystem in Userspace) to access remote files because FUSE wouldn't work on all their platforms (back in 2006). Instead, KDE rolls its own remote access solution which only truly works with KDE-aware applications. In contrast, GNOME uses FUSE behind the scenes so that non-GNOME can seamlessly access the remote files.
So, KDE refused to use FUSE because that was too linux specific (at the time) but now requires systemd? Ugh.
I don't have a problem with systemd, and I'm all for focusing on functionality for the setups that most users actually use (e.g. Windows' lack of FUSE shouldn't stop KDE from using FUSE on Linux, BSD, etc.), but they should come up with a consistent policy for when they rely on an external dependency and when they don't.
(Aside: I wish there was some way users could fund fixes for specific bugs/implementation of specific features on KDE. That way we wouldn't have to wait a decade to get features users have been clamoring for.)