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 377137
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Great!
by superstoned on Wed 5th Aug 2009 09:20 UTC in reply to "RE[4]: Great!"
Member since:

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 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:

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

RE[7]: Great!
by mat69 on Wed 5th Aug 2009 18:00 in reply to "RE[6]: Great!"
mat69 Member since:

That would in fact be one way.

Though experience shows that once a hack is in it takes pretty long to get it removed --> look at the hacks in KDE 3.
Especially if people denied there was a bug at all in the beginning. They would simply say that the hack "fixed" the bug and the bug was in your application so no need to change anything in their code.

"As long as it 'works' there is no reason to change it." (not a quote! rather a way of thinking)

Reply Parent Score: 5