All you need to know about systemd is that ironically systemd

File: katedru.gif (40KB, 1968x639px) Image search: [Google]

40KB, 1968x639px

All you need to know about systemd is that ironically systemd wouldn't be able to exist today if we had been using systemd's design philosophy on GNU/Linux from the beginning.

In other words, we'd be stuck with outdated technology and only able to replace it if we create another monolithic init system that interacted with everything in exactly the same way systemd does.

Systemd is basically exploiting the flexibility of its predecessors to kill the flexibility we have in the area of init systems. People might like it now, but we're walking into a walled garden.
After systemd becomes the standard and everything depends on it systemd will never receive any competition because it would be an extremely monumental task to try and create a systemd alternative.

All the newbies here support systemd because it "just werks". But using things just because it works is a very Windows mentality.
They're forgetting (because init systems isn't really on their radar in the first place) that the reasons we all use GNU/Linux in the first place is for flexibility, being able to do things _our_ way not the way someone getting paid to do their job decided we should do it, and design philosophies.
Systemd is the exact opposite of all of that.