Linked by suka on Thu 25th Aug 2011 22:19 UTC
KDE "After years of focusing on further improving KDE4 two weeks ago the developers of the free desktop announced the next big step for their project: KDE Frameworks 5.0. But as long-time developer - and Plasma team leader - Aaron Seigo points out in an interview with, the source-incompatible changes shall be held to a minimum. Also calls Frameworks 5.0 only the "first step", new Applications and Workspace releases are to follow later, Seigo goes on to talk about the chances in the mobile market with Plasma Active and further areas of collaboration with the other big free desktop: GNOME."
Permalink for comment 487338
To read all comments associated with this story, please click here.
Member since:

Yeah sure... your netbook has a GPU and either a 1.6Ghz single or dual core cpu and at least 512Mb ram... perhaps you should reread my post KDE3 does run on alot crappyier hardware hardware that is is respectively also a lot cheaper and energy efficient.

lemur2 ... sigh clearly you have no idea who you are talking to and the lengths I will go to run run what I like ;) KDE 3.5 on Gentoo on an 800Mhz Crusoe runs nicely with jumanji as my browser or opera. It has some opengl acceleration but its pretty minimal.

I find it a valid critisism because there is no reason many of the features of KDE4 cannot run on older hardware... I triple boot XP, Gentoo and svn builds of Haiku OS on the subnotbook I was referring to and the latter has lots of impressive features that even KDE4 lacks like window stacking and tiling that makese sense super fast file searches that doens't bog everything down with nepomunk and clucene based text searches that are also impressively fast.

KDE 3.5 is nice and I like it but I would have liked to have seen an IMPROVEMENT without degradation in performance and no it wasn't too much to expect KDE developers themselves have as time passes even fixed some of the performance regressions they have introduced like the data base backends for plasma I believe it was was quite io bound for no real reason things like that add up massivly especially in a huge project like KDE and throwing cycles or disk io at a problem is not a solution.

Reply Parent Score: 1