a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
https://www.sambent.com/the-engineer-who-tried-to-put-age-verification-into-linux-5/
The Engineer Who Tried to Put Age Verification Into Linux

Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.

Sam Bent

@leyrer i think way too many things are in systemd that should be seperate daemons.

Its the reason why i dislike systemd. Oh also Lennart.

But yeah, not really a lot of choice we have.

@leyrer I mean i am old enough to remember the drama with encrypted wifi.

So i get that part. Systemd has improved that.

I also understand the mounting part of devices that might be unplugged.

ok. Maybe also that has been approved a bit by systemd.

Most that came after that i don't like to be in systemd.

@mcfly @leyrer: IMHO we have a lot of choice: There are at least half a dozen other init systems out there and in at least some Linux distributions, you can choose your init system. Plus dozens of container init systems. There also several systemd-free Linux distros. And there are BSD systems.
@mcfly @leyrer Thank goodness for System V init, BSD init, OpenRC, dinit, runit, and so on. :3