Linked by Thom Holwerda on Sat 24th Nov 2007 23:31 UTC
Thread beginning with comment 287137
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
> was a mess by it self that needed to be rewrited,

no, actually, it was serving kde users and developers just fine. when we switched to d-bus, we actually had to push for and implement a large number of improvements to the tool chain around d-bus and in d-bus itself to get even near where we were with DCOP. d-bus is the right way to go (i was one of the early advocates even) but it's not because it's more mature that DCOP was.
there are some nice new features that come with d-bus (i've personally enjoyed exploiting a few them =), but DCOP was still very solid.
and yes, d-bus built on the lessons from dcop. that's why it looks a lot more like dcop than, say, bonobo.
> hey, I wasn't me who says so, read the DCOP mailing
> list.
which dcop mailing list would this be? and which mails to it? or ... are you just writing what you think sounds good?