dbus-broker

Activity, over time

Daily GitHub activity and social mentions.

Mentions

Daily posts linking to this repository

Loading mentions chart

Attention

Daily stars & forks

Loading attention chart

Star accumulation

Cumulative stars

Loading star accumulation chart

Pull requests

Daily opens & merges

Loading pull requests chart

Conversations

Daily issues & comments

Loading conversations chart

Community

Daily accounts & reviews

Loading community chart

Mentions

1post · 30d
Nov 70 posts
  1. Lobsters · · on D-Bus Hell · ~regalialong

    This might be revisionist since I wasn't around for the fights, but I think the criticism is split on Dbus the implementation and Dbus as a concept. There were quite a few fights around the implementation of D-Bus itself, as dbus-daemon which provided it was slow and with design faults. A few ideas were thrown around, causing the most fights being moving dbus into the kernel, that is kdbus. [probably the most revisionist statement here] I believe the topic basically died with bus1/dbus-broker which is a high-performance drop-in replacement for dbus-daemon, do read its announcement post here. I think back in the day you'd shake your fist at the clouds and complain that things were fine with pure sockets before, but nowadays I don't think about the daemon anymore. At all. (hooray ^^) For the protocol, I hate citing Vaxry but he's the loudest opponent I can remember, he disliked the underdocumentation of the protocol and that it encoded the types in the wire protocol itself. I'm fine with linking someone else with other criticism.

    8 points

Latest stargazers

The last 10 distinct accounts we observed this year.

Most active participants

PR, issue, comment & review events in the past year.

Packages

Scan pending.

Live mentions badge

Show how many posts mention your project in the last 30 days.

Live mentions · last 30 days