Linked by Eugenia Loli-Queru on Wed 13th Sep 2006 02:24 UTC, submitted by superstoned
This article is about KDE's memory usage, but there are comparisons with other solutions for your desktop. Lubos Lunak concludes there is still work to do and there is some lowhanging fruit, but KDE does already a nice job on keeping its memory usage low.
Permalink for comment 161992
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-10-19
> You obviously don't understand C++. KDE classes are subclasses from the Qt classes in most cases. So even though you don't see something like a QWindow in the code, a KWindow is using the members and methods of that Qt class.
Just to clarify: While many classes in kdelibs are indeed augmented subclasses of Qt classes, that doesn't mean applications always need to use them or that applications don't use many other Qt classes directly (you didn't contradict that, of course, just wanted to make it clear for the discussion).
In fact, as Qt has taken on more of what kdelibs used to do in version 4, quite a few kdelibs classes are being retired in favor of new Qt4 classes for KDE 4 - shifting the focus of kdelibs a little bit more towards high-level frameworks, perhaps.