Activity, over time
Daily GitHub activity and social mentions.
Mentions
Daily posts linking to this repository
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
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
Mentions
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.