Posted Mar 5, 2012 7:11 UTC (Mon) by khim
In reply to: Point optmization?
Parent article: Speeding up D-Bus
At least Glibc gets used and shared by most programs, dbus isn't.
Actually dbus is already used by a lot of programs and I suspect in the future it'll be more fundamental, not less:
$ ldd /usr/bin/* | grep libc.so.6 | wc
1181 4724 59026
$ ldd /usr/bin/* | grep libdbus-1.so.3 | wc
196 784 11760
From this POV it's size is not excessive and before we can talk about just sad it's always a good idea to compare “bloated pig” with “lean and mean” alternative. In case of GLibC it's size justified not by the fact that it's most popular Linux libc, but the fact that it's the only one with efficient threading, adequate i18n, etc. Oh, and significant piece of GLibC is backward-compatibility functions: today's GLibC is still compatible with all the programs compiled decade ago (and more). This may be insignificant advantage for you, but for me it's important. What's your alternative for dbus and how it compares to dbus feature-wise?
to post comments)