Any actual arguments against systemd?

It's large. Much larger than a simple init should be.
A lot of its parts should be (and were before pottering) separate projects.

>Corporate = Government
ancapistanis don't even know what to spout nowadays

Oh yeah, and how about that time with efivars being constantly mounted read-write and pottering refusing to fix that?

without-systemd.org/wiki/index.php/Arguments_against_systemd

What, bricking motherboards isn’t a good enough excuse now?

I don't like it at all, I think Linux will regress with that really fast
- fucking journald use binary files, fucktards found a way to put colors and events in a binary files, they could fucking use a text file or json in worst case scenario

- is bloated for good

- try to replace things that are alreayd working

i dont like it at all, there are so many reasons that i can't even continue

This is straight out of 2012 and most of these arguments aren't valid anymore.

Myth: systemd is a feature creep.

Well, systemd certainly covers more ground that it used to. It's not just an init system anymore, but the basic userspace building block to build an OS from, but we carefully make sure to keep most of the features optional. You can turn a lot off at compile time, and even more at runtime. Thus you can choose freely how much feature creeping you want.

have you tried anything else? if you haven't tried init scripts, you won't really know what's so akward about systemd

most of arguments are still valid, systemd is a monolithic shit

The network manager sucks.

>It's against Unix philosophy
Hurr dur dur '''Unix Philisophy'''
I prefer the '''it fucking works''' philosophy.

Attached: 1499802634284.jpg (439x290, 23K)

GNU's not unix.

those who dont understand unix are condemned to reinvent it, poorly

Why don't you buy yourself a macbook and get the hell outta here then

I don't like it

Uses (((googles))) name servers as fallback by default.

Also, it's bloated.

could somebody ELI5 what it actually do?