Earlier quoted context omitted.
Could you try to make that point again but without the hyperbole and with some specifics? It's possible you're trying to engage in a real discussion here but it reads like you're just venting.
I believe it deserves as much respect as the systemd maintainers treat their users with. 1. Hosed system down. All systemctl commands fail with "Failed to get D-Bus connection: Operation not permitted". Only option was to reinstall it from scratch, like a Windows machine 2. Does something wrong. So many random weird bugs like "failed to start reboot.service" ffs. Answer is always "upgrade systemd" which is a problem…
It really doesn't. One of the pull requests they link to as the "lamest vendor response" literally has only three comments from Poettering, one which says "Looks great otherwise", one which says "excellent! thanks a ton for fixing this!", and one which answers a question about why a local variable is named MTU.
Seriously, this is the thread itself: https://github.com/systemd/systemd/pull/6214
There's another linked thread where he admits that they misjudged a commit as irrelevant, but explains that they can't rewrite git history, which is unfortunate but hard to take serious issue with. And a third where he says that systemd will defer to validating input according to POSIX and other common cross-distribution requirements, instead of enforcing its own, stricter set of requirements that would actually break other systems.
It's not even hard to find places where Poettering has said something that makes him look less sympathetic than this stuff. But referring to these as the "lamest vendor response" really just makes it look like they're searching for anything to take issue with for Poettering himself, regardless of the topic at hand.