The Grumpy Editor's guide to surviving the systemd debate

So what's the existing portable non-dbus DNS management API that they're replacing? For that matter, what's the dbus-based DNS management API that they've added? (I can't find any docs describing such a thing on the systemd website, but am not an expert on DNS stuffs.)

OTOH I don't see how you can claim logging as an example; systemd 100% supports the standard syslog API. They also provide some additional APIs that let you provide extra structured metadata that syslog just can't handle (so it's not really "replacing [an] existing API", it's new features entirely), but even here it would be trivial for users to include a stub implementation of this API that falls back on throwing away the metadata and calling syslog() if the journal isn't available. Heck, it'd be like a 10-line patch to teach sd_journal_sendv to just do this by default. (Also there's zero dbus involved, just good old fashioned AF_UNIX sockets like Allman intended.)