4 ms·

I think this type of comment ought to have a bit talking about *why* you would reach for it.

• charcircuit 3y ago
  It's convenient when most services on the system can all talk the same protocol. It means that services can be more easily secured because they aren't all making other own protocols from scratch. Making your program talk to various services is easier when you can use the same library and there is no need to roll your own because some service decided to make up its own custom protocol for some reason. Imagine if websites would all roll their own protocol instead of using a standard like HTTP. Having a standard IPC protocol also makes debugging easier since it makes sense for their to be real tools for seeing what's going on. Improvements to the implementations handling the protocol can make improvements throughout the whole system. There are network effects in everyone using the same protocol. If you want to step out of this ecosystem and build your own IPC protocol then you need to justify what you are gaining for the value you are giving up.
  • zlg_codes 3y ago
    The downside here is, should any vulnerability be found in the One True Implementation, every consumer is now vulnerable as well. Just as you shouldn't let a crop go monoculture, your software should not all be built on one or two pieces of tech. What happens when dbus is replaced? Now you have to move onto the new, broken thing, and change your code to adapt, giving control to others over your program. There are valid reasons to not just cargo cult dbus.