(26-10-2020, 10:56 PM)Ramiferous Wrote: Can you explain why? This was asked on Reddit but didn't get a response.

D-bus is often missused in a lot of applications as a transport protocol instead of being used for RPC. It's not meant to be fast nor efficient. But then you see applications that spam battery status every second, which this isn't meant to be something d-bus do.

D-bus is a middleware that provides interfaces that software could possibly provide, on a contractual basis. When it comes to notifications, it standardize the interface and say "whoever attaches as the notification receiver will respect this interface", found here.
It also has good introspection capabilities to explore what services attached to the bus provide. Like for example, on IRC we were discussing how Firefox implemented the MediaPlayer2.Player interface, allowing you to remotely control the videos playing within Firefox through d-bus.
That's my 2 cents after writing this summary.