Hacker News Reader

throwway120385

DBus is yet another message bus, but this time for a few desktop applications. Made famous by BlueZ's requirement of DBus and by it being the only Linux userspace thing that made it into Android before they completely rewrote the userspace stack for the phones.

A ton of "desktop linux" components will attempt to use DBus for inter-process communication because it's easier than a lot of the alternatives.

View on HN

Eh, some of us would wonder what the easier alteratives are?

Unix domain sockets or FIFOs could be an alternative, but you'd have to do all kinds of complexity to support pub/sub style many to many communication over them (which is what dbus effectively does for you).

It depends if you are a fan of a centralized server vs decentralized communication.

Anyway, all the complexities of using sockets/FIFOs could be hidden inside libraries.

Once you hide the complexities of using sockets you just end up with some sort of message bus that each application connects to and registers an ID with... which is essentially what dbus is.

I specifically said libraries (as opposed to a centralized service).

Reply on news.ycombinator.com