Linked by Thom Holwerda on Thu 2nd Apr 2009 16:12 UTC, submitted by Rahul
Permalink for comment 356610
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
More News »
Sponsored Links



Member since:
2006-02-04
Think about when jumping GTK1 to GTK2.I think that was a mess too.
Form development point of view, stick to old library means we have to deal with potential legacy/ugly code when implement new ideas. And difficult for newbie to contrubute.
Think about the delay of Xorg 7.5. X works for decades. It take afford to implement new feature based on old code. That's why Wayland comes out.(Although it is not a replacement for X, but Wayland make it a lot easier to implement modern stuff).
KDE4 needs a bebase/rewrite to incorporate new things, so there it went.
No one knows when GNOME needs too.
GNOME and KDE are just two different ways of how FOSS evolve.