[caiocaiocaio]

Building a Linux distro was like playing with Lego: the pieces were very interchangeable (in practice there were difficulties, but usually ones that were fun and rewarding to resolve; "fun and rewarding" is the exact opposite of SystemD).

SystemD also fails quietly or with useless errors and makes problems hard to diagnose - so a bug not directly caused by SystemD looks like it comes from SystemD because SystemD slime is on everything - is extremely poorly-documented, extremely over-engineered, and subject to rapid change due to the moodiness and instability of the OverPoetter.

[luckycharms810]

I will say on the flip side - Going from cron jobs to Systemd timers has been super helpful. You can use journalctl to track the output and find pesky issues like difference in shell, missing environment variables, file permission issues.

[atonse]

Can you expand on what you feel is over-engineered?

[esarbe]

Your name-calling disqualifies you and discredits any valid argument you might have had.