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 161990
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-10-19
> It is kind of the opposite of what KDE is doing, which is building a platform on top of a toolkit, with a lot of duplication; GNOME is building the toolkit to be the platform.
May I ask you to elaborate on that? Because I'm not seeing it. kdelibs duplicates rather little of what Qt is doing; it extends and augments it, and adds several completely own frameworks. In the KDE 4 development cycle, a lot of kdelibs code is being retired in favor of new Qt4 classes that have been newly added to the Qt toolkit, so that kdelibs can concentrate on other tasks.
Heavy code reuse is one of the core tenets of the KDE programming model - have a look at its strong component model which was designed to facilitate this, for example - and duplication is generally avoided unless practical necessity.