Linked by Kroc Camen on Sun 29th Nov 2009 20:02 UTC, submitted by fsmag
Permalink for comment 397114
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 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2009-02-19
Just to throw this out, I think the real problem is a lack of high-level interface standards, not the existence of multiple desktops environments (and multiple sound servers and multiple network control daemons and etc.). If there existed one single, high-level, lowest-common-denominator API for basic (themed) windowing, that every other windowing kit and DE could export (in addition to their own API), then having multiple desktop environments wouldn't be a problem at all. Similarly, if there existed one standard, high-level sound API that every sound system could export, then it wouldn't matter (well, it wouldn't matter as much) what lower-level sound system was actually in use. Most of this mess would go away if we just had standard interfaces for Desktop system tasks that whatever implementation you choose could export.