Linked by Thom Holwerda on Sat 26th May 2007 20:18 UTC, submitted by GhePeU
The GNOME Community Roadmap is a big-picture view of functionality we expect GNOME to include in short-term and long-term future. The roadmap is based on feedback from current GNOME developers and other community members. This roadmap shows the ideas and hopes of GNOME contributors for the near future.
Thread beginning with comment 243891
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.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-07
OK, you got a point, Gnome first uses a seperate lib to test something, then it gets included. Makes sense.
And that's just not true. KDE is very carefull about what gets in KDElibs. That's why there are the 'layers': something must first be used in an app, then it goes to the base library of that component (eg libkdeedu, libkdegames, libkdepim), then it can go in kdelibs (if there are enough users -> this process is DEMAND driven), and finally, Trolltech might adapt it into Qt.
Having seen the discussions about adding stuff to the KDE libs, I can assure you - this is a really tedious process, involving many people and sometimes harsh reviews. And apparently, this process does work a lot faster than the Gnome one, as editable toolbars aren't really 'new' in KDE.
It IS true that you can't start a KDE app without loading a lot libraries currently, though not to the extend you seem to think. And KDE 4 is modularizing KDElibs much more, just like Qt got more modular.
So in a nutshell, KDE got a modular, high-quality, very complete set of libraries, lightening the load of application developers. And I think I can say it is ahead of Gnome in this area (and ahead of Windows and Mac OS X, btw, though in all 3 cases, not in every area).