[myusernameisok]

> Why is that now a systemd thing? Just cause systemd is the creepy uncle that likes to touch everything it can? So I'm just gonna pipe that crap into syslog anyway... and don't get me started on LP's shenanigans.

Feature creep falls under the umbrella of sticking to the UNIX philosophy too closely, the first point of the UNIX philosphy is:

> Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new "features".

In any case, I think it's arguable if it's feature creep or not. The goal of an init system is to start your system up, it makes sense that the thing that starts daemons would also monitor them, take logs, and do other support actions as well.

The only complaint I actually agree is that systemd/journald uses a binary format to store logs, but I don't think that's a good enough complaint to warrant all the hatred.

[concede_pluto]

The goal of an init system is to start daemons. It shouldn't have any opinions about which daemons you run, and it has no business doing random tampering like intercepting logins and DNS requests and renaming device nodes. Breaking "nohup foo & logout" is shockingly inappropriate; end users should never ever care how an admin may have booted the system much less have to know how to interact with it!

[myusernameisok]

> it has no business doing random tampering like intercepting logins and DNS requests and renaming device nodes

I agree with the resolving DNS requests complaint, wasn't aware of that to be honest. That actually does seem somewhat odd.

However the other two make sense, systemd is used to init your system. Supporting login functionality as well as mounting and managing devices through udev (which supports renaming devices, as you said) doesn't seem too odd to me.

> Breaking "nohup foo & logout" is shockingly inappropriate;

Can you explain this to me? I never heard about this and my googlefu isn't returning anything fruitful.

> end users should never ever care how an admin may have booted the system much less have to know how to interact with it!

Unless you have an advanced user running `systemctl --user` or trying to check logs then I highly doubt the average user will need to know which init system you are using. For the most part, if you are just using your computer as a facebook/youtube/netflix machine then you probably don't care about the init system your computer is using (which I suspect describes 75% of users), assuming you even know what an init system is.

[JdeBP]

systemd and nohup:

* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221

* https://news.ycombinator.com/item?id=11797075

* https://news.ycombinator.com/item?id=11782364

systemd and Netflix:

* https://news.ycombinator.com/item?id=14837110

* https://www.theregister.co.uk/2017/07/24/underscore_domain_n...