Linked by Thom Holwerda on Sun 18th Jun 2006 14:26 UTC
Thread beginning with comment 134789
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2005-08-28
KDE, as in what the KDE project itself provides, is as complex and full-featured (or bloated if you prefer) or as light as the distributor that's compiling it for you chooses to make it. One of the really nice things about it, is how they provide there source tarballs in easily understandable divisions, with clear instructions on how to compile. The bare minimum is really just qt, kdelibs and kdebase. Add to that, the really nice feature of DO_NOT_COMPILE=foo,bar argument that you can prefix your configure with do enable to you to trim each of them to your liking, good stuff.
No, it isn't and likely never will be as light and thin as something like fluxbox or wmii, but that's not what it's meant to be.