Linked by Thom Holwerda on Thu 2nd Apr 2009 16:12 UTC, submitted by Rahul
Gnome Only a few days ago, we ran an article on the future of KDE and GNOME, and which of the two had the brighter future based on their developmental processes. Barely has that discussion ended, or the GNOME engineering team comes with a pretty daunting plan to introduce a fairly massive reworking of the GNOME interface for GNOME 3.0 (2.30). Read on for the details.
Thread beginning with comment 356542
To read all comments associated with this story, please click here.
Comment by kaiwai
by kaiwai on Thu 2nd Apr 2009 23:12 UTC
kaiwai
Member since:
2005-07-06

I like this here:

"move all of the deprecated libraries out of the platform, so people stop using them in new code"

What they need is a 2 release cycle where they say that a api is deprecated and it is totally removed in 2 releases (deprecated for example in 2.24 and totally removed in 2.28) that gives the relevant project over a year to upgrade their code, which imho is more than enough time.

Reply Score: 3

RE: Comment by kaiwai
by elsewhere on Fri 3rd Apr 2009 04:48 in reply to "Comment by kaiwai"
elsewhere Member since:
2005-07-13

What they need is a 2 release cycle where they say that a api is deprecated and it is totally removed in 2 releases (deprecated for example in 2.24 and totally removed in 2.28) that gives the relevant project over a year to upgrade their code, which imho is more than enough time.


If you're going to break API compatibility, then that should be a major-version upgrade. You can add to them, but API's shouldn't break in point upgrades.

For better or worse, the blogosphere was outraged that KDE released a developer preview as a final version with 4.0. That would be a tempest in a teapot compared to the outcry if Gnome starts breaking compatibility with incremental upgrades and starts confusing the hell out of everyone as to what libraries and APIs should be used with which point version.

Just my 2c.

Reply Parent Score: 4

RE[2]: Comment by kaiwai
by kaiwai on Fri 3rd Apr 2009 06:04 in reply to "RE: Comment by kaiwai"
kaiwai Member since:
2005-07-06

If you're going to break API compatibility, then that should be a major-version upgrade. You can add to them, but API's shouldn't break in point upgrades.

For better or worse, the blogosphere was outraged that KDE released a developer preview as a final version with 4.0. That would be a tempest in a teapot compared to the outcry if Gnome starts breaking compatibility with incremental upgrades and starts confusing the hell out of everyone as to what libraries and APIs should be used with which point version.

Just my 2c.


You need to re-read what I wrote because in no place did I advocate a KDE 4.x solution. I stated that deprecated parts should be gradually removed not all at once - and not until a superior and stable replacement has taken its place. KDE 4.x was a Bennite solution to something that could have been done via evolution rather than a 'great leap forward' with the body count of many behind the change.

Reply Parent Score: 2

RE[2]: Comment by kaiwai
by sbergman27 on Fri 3rd Apr 2009 23:21 in reply to "RE: Comment by kaiwai"
sbergman27 Member since:
2005-07-24

For better or worse, the blogosphere was outraged that KDE released a developer preview as a final version with 4.0.

Not just the blogsphere. Pretty much everyone noticed that they were so anxious to get out their Gnome killer that they shitted all over themselves in the process.

Reply Parent Score: 0