i wonder if the tire fire that is systemd happened because linus didn't ever take ownership/responsibility for a userspace and just punted that forever to GNU (which has always sucked and will always suck)
@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.
@sneak all of that led to me choosing Go. I'm writing statically-linked binaries that talk to the kernel and can mostly ignore whatever distro drama is getting whipped up by the usual suspects.
@alrs yes, independent processes that never talk to anything else but the kernel are great. i'll be over here on macos where my contact database can talk to my messenger can talk to my notifications system can talk to my data indexer, getting work done. dbus exists for a reason and there is more to computing than making only syscalls from your statically linked binaries. i entirely reject the primitive 1980s unix worldview.
