Linked by Thom Holwerda on Sun 10th Oct 2010 14:17 UTC, submitted by Extend
Permalink for comment 444781
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-06-29
Don't lie. I've written quite clearly what the issue is: Kwin. It might sound like just one component, but the problem with Kwin is that once Kwin has issues, it permeates into everything else. If responsiveness is bad, everything is bad. If, in this day and age, you can't even code a properly responsive desktop (and I've yet to find the magic driver/hardware/distribution/KDE version combination that is responsive), then you've got problems - major problems.
The interesting thing is that I've had KDE developers confirm to me that Kwin simply has a lot of performance problems - so the people who actually code for KDE know there are problems. It's always the armchair folk such as yourself that gets all their panties in a twist because he can't grasp that there is a sizeable number of people who are experiencing problems with Kwin.
From day one, I've been extremely positive about KDE4 as a concept, and the progress has been phenomenal. It's just that Kwin is lagging behind (literally), but because it is such a vital component, it shows in daily use quite clearly. Moving windows around, opening menus, minimising/maximising, resizing - things you do all the time - things that add up.
KDE/Qt is miles ahead of GNOME/Gtk+ (both are miles behind Windows 7, mind) - it's just that when I have to choose between technologically advanced but unresponsive, or crude but responsive, the choice is simple.
Edited 2010-10-11 14:52 UTC