On Thu, 11 Feb 2010 02:31:21 -0500, Walter Dnes wrote: > > Because nine years ago, Linux desktop software didn't use > > interprocess communication. Of course things will still work, but not > > necessarily everything. For example, Network Manager uses D-Bus to > > tell programs when your Internet connection is available and not, so > > your mail client goes into offline mode rather than pointlessly > > trying to access your mailbox. KDE4 uses it quite extensively, ust as > > KDE3 used DCOP. > > There is too much solution-in-search-of-a-problem here.
Hardly, IPC is harrdly new, the amiga was doing ti 25 years ago and shortly after that it became available to user scripts. > XMMS followed > the original Unix philosophy... it did one thing did it right, namely > playing audio. Yes, and if you have a number of programs, each doing one job only, they need to be able to communicate in order to do the larger job. Imagine a building site where the bricklayers, plasterers, electricians an plumbers didn't talk to each other or the project manager. In a shall, pipes can be used for IPC, but that doesn't work on a desktop so something else was needed. This has always been true, all that is new(ish) is that D-Bus is now the something else, and it is a global standard. DCOP was good, but it only worked with KDE programs, D-Bus means that your system is just that and not a bunch of programs each going their own way, ignoring each other and duplicating effort. If you want an OS like that, I hear they produce one in Redmond. -- Neil Bothwick If it isn't broken, I can fix it.
signature.asc
Description: PGP signature
