>> Same here, if systemd was just an init system, i d probably still
>> avoid it and fight it, but the main problem is that its much more than
>> that, eating everything around it (
>> http://neofutur.net/local/cache-vignettes/L200xH133/arton19-b28db.gif
>> ), and that is the main problem, for sure.
> In case you like a nice piece of irony: Both GNOME and KDE perform like
> shit. According to the opinion of both the GNOME and the KDE developers,
> the reason for this must be somewhere in all the code they didn't
> write. Hence, it has to be replaced. Especially considering that it's
> all "But that's not how Microsoft does it!" stuff --- and you can't get
> more fishy than that, can you?

sure, and that is one more reason to prefer trinity ( kde3 fork ),
functional, intuitive, stable, not eating all your ram and . . . with
developpers who clearly stated they wont add any dependencies to
systemd ;)

anyone here who havent already tried trinity, just give it a chance :
https://www.trinitydesktop.org/
binaries available for most distros :
https://wiki.trinitydesktop.org/Category:Documentation#Installing_from_a_Package_Manager