@sneak I don't think I'm the only person who made the move from sysadmin to full-time developer after systemd showed up.
@alrs systemd is a mediocre attempt to fix the clusterfuck failure that is linux's de-facto userspace. it's not great but it's not terrible; the people who oppose it are doing so based on tradition grounds ("my userspace has always sucked and i hate anyone who tries to de-suck it and thus forces me to remember that the BSDs exist with non-shitty userspaces"). if linus had actually took responsibility for an OS instead of just the kernel, things would be better.
@sneak If systemd didn't touch logging I mostly wouldn't care. The strongarm move into Debian kinda killed Debian for me. I still use it, but now releases are depressing, not exciting.
@alrs i am not interested in your partisan minutiae. it does not matter what systemd touches or does not touch. it's a bazaar, remember? there are like a thousand distros, including like a dozen that only exist as examples of permanent poettering-rage.
it's all just an example of linux idiots embracing worse is better "because this is how we've always done it".
@sneak kinda, except now you're on the hook for keeping up with the mailing list for every library in every container, and you're back to Slackware ca. 1995. We couldn't keep up when it was one admin per machine back then, now that it's one admin for hundreds or thousands of machines.