Linked by Thom Holwerda on Wed 5th Aug 2009 00:12 UTC, submitted by rexstuff
KDE The KDE team has released KDE 4.3. This release comes packed with improvements and bug fixes - in fact, over the last six months, 10000 bugs were squashed, 2000 feature requests handled, and 63000 changes were checked in by 700 people. We've already talked about this new release in quite some detail last week, but let's take a look at the most important new features anyway.
Thread beginning with comment 377091
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Great!
by bnolsen on Wed 5th Aug 2009 03:58 UTC in reply to "RE[3]: Great!"
bnolsen
Member since:
2006-01-06

QT4 over engineered their rendering engines. They did it to get all the fancy effects like AA, composing, etc. Unfortunately they tanked their performance for CAD type applications and pretty much tossed any hope of running remote display/remote terminal applications.

It's a shame and probably all this stuff needs to be ripped out, refactored and dramatically simplified, like the whole rest of QT.

Reply Parent Score: 4

RE[5]: Great!
by Messere on Wed 5th Aug 2009 06:26 in reply to "RE[4]: Great!"
Messere Member since:
2006-10-12

QT4 over engineered their rendering engines. [...] and pretty much tossed any hope of running remote display/remote terminal applications.


So true.

NX client connected to kde4 is unbearably slow compared to kde3 on the same network link. And it gets even worse with "raster" rendering enabled.

Reply Parent Score: 4

RE[5]: Great!
by superstoned on Wed 5th Aug 2009 09:20 in reply to "RE[4]: Great!"
superstoned Member since:
2005-07-07

Over engineered - well, yes, that's one way of looking at it. You could also say they developed a rendering engine capable of using the latest hardware acceleration features available. Those features (still) don't work properly on linux (no problem on win and mac, btw) so now it's up to the X.org devs and driver developers to fix their software.

KDE isn't an operating system, you know. We build upon what is provided by the platform - and if the platform provides a sucky infrastructure, our performance suffers. And in the interest of moving forward, we refuse to work around bugs in the lower stack - we'd rather see them fixed. Sorry for that but we believe progress needs a strong platform. And those features we're gonna need in the future won't be done properly i we don't put some pressure on those working on it.

Reply Parent Score: 15

RE[6]: Great!
by Tuishimi on Wed 5th Aug 2009 16:09 in reply to "RE[5]: Great!"
Tuishimi Member since:
2005-07-06

Why not meet halfway by implementing some "cheap hack" to speed it up, one that can be pulled when the underlying infrastructure improves? It could be part of the regression testing with each build/release cycle to run without the hack and with the hack to check for the performance levels.

Reply Parent Score: 2