mircea_popescu: but anyway, systemd is what, the pulseaudio guy and this guy, right ?

mircea_popescu: apparently systemd devs have all the love and support they could use lol.

mircea_popescu: https://wiki.ubuntu.com/systemd << not even ubuntu uses it o.O

mircea_popescu: "11. Ultimately, systemd's parasitism is symbolic of something more than systemd itself. It shows a radical shift in thinking by the Linux community. Not necessarily a positive one, either. One that is vehemently postmodern, monolithic, heavily desktop-oriented, choice-limiting, isolationist, reinvents the flat tire, and just a huge anti-pattern in general. If your goal is to pander to the lowest common denominator, so

mircea_popescu: "systemd clusters itself into PID 1. Due to it controlling lots of different components, this means that there are tons of scenarios in which it can crash and bring down the whole system. But in addition, this means that plenty of non-kernel system upgrades will now require a reboot."

mircea_popescu: "It's also worth noting that systemd will refuse to start as a user instance, unless the system boots with it as well"

mircea_popescu: By default, systemd saves core dumps to the journal, instead of the file system. Core dumps must be explicitly queried using coredumpctl4. Besides going against all reason, it also creates complications in multi-user environments (good luck running gdb on your program's core dump if it's dumped to the journal and you don't have root access) ☟︎

mircea_popescu: systemd's journal files (handled by journald) are stored in a complicated binary format2, and must be queried using journalctl. This makes journal logs potentially corruptible, as they do not have ACID-compliant transactions. You typically don't want that to happen to your syslogs. The advice of the systemd developers? Ignore it. No, seriously. Oh, and there's embedded HTTP server integration (libmicrohttpd). QR codes

mircea_popescu: "1. systemd flies in the face of the Unix philosophy: "do one thing and do it well," representing a complex collection of dozens of tightly coupled binaries1. Its responsibilities grossly exceed that of an init system, as it goes on to handle power management, device management, mount points, cron, disk encryption, socket API/inetd, syslog, network configuration, login/session management, readahead, GPT partition disco

mircea_popescu: "We do recognize the need for a new init system in the 21st century, but systemd is not it."

mircea_popescu: "Avahi is another Lenart Poetteing idea - like Pulse audio and systemd. These aren't bad ideas at all, but the implementation of each one has been a big headache. So submitting a bugzilla report that Lenart must address is a good way to slow/prevent the next 'Poetteing invention' from causing havoc."