Linked by Thom Holwerda on Mon 14th Mar 2011 18:59 UTC
Thread beginning with comment 466238
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.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-06
An implementation detail that happens to be very important for users, because XEmbed is widely agreed to have a great deal of things wrong with it.
The question is, what replaces it? Does it get replaced by something that desktops and applications can agree on and communicate through and work with or do we go the traditional Unix and CDE route with a a ton of fragmentation that provides no benefits to anyone?
You know fine well why Aaron specifically mentioned D-Bus in what he wrote. Do we really need to go over why D-Bus was initiated and what benefits common communication between differing applications and desktops brings to users?
I think you're just digging a bigger hole here Dave, and it's sad to see.