cwizardone |
04-01-2018 11:40 PM |
Quote:
Originally Posted by enorbet
(Post 5838346)
The bulk of conflicts I experience is due to employing KWin. Several of XFce's "Settings" tools won't even launch which may be a good thing in the longview but it is a bit confusing which set of "Settings" to use for a specific job or effect since they overlap quite a bit. If there was a major difference in performance I might be able to accept that extra effort but since there is now so little, it just isn't worth it to me. I'm not at all in love with Plasmoids and it would be nice to have a little more understanding of exactly which parts of Akonadi I really need but what little tweaking I've done results in a Desktop at rest of about 3% CPU and 6% RAM with KDE 4 and Plasma 5 flavors I've tried get that with no interference from me. So I'm guessing KDE has been listening and responding.
|
I've not used KWin with Xfce, but I have noticed KDE-4 picks up a few of the Xfce settings when I move to KDE and don't first 'turn off' the Xfce Application Autostart "switches." The few I've seen KDE "pull in" from Xfce are Xscreensaver, Clipman and a start up audio script.
OTOH, Xfce never "pulls in" anything from KDE.
There was a time when kde did consume a great deal more resources than Xfce, but you are correct, that hasn't been the case for several years. I use to track it and write it down and the results were very close between Xfce and kde-4. That said, regardless of what the various utilities report, Xfce does launch applications notably faster than KDE.
The leather-dark theme is so pleasing to my eyes, I've stopped using KDE almost entirely and plan not to install kde-5 when Slackware makes the change.
If you are not indexing your hard drive and/or using KMail/Pim, you don't need akonadi. One of the first thing I do with each fresh installation is uninstall akonadi, but "removepkg" does not, for whatever reason, remove the executable files and you have to go into /usr/bin and delete them manually.
;)
|