Okay, so I just spent a huge amount of time reading correspondence from Poettering(systemd dev) to the debian team about a single tiny little script in systemd.

Why is systemd a thing? Their scripts make things endlessly complex. Little scripts double in size. Tiny C modules triple in size, just to account for the complexity of systemd.

What ever happened to the Unix Philosophy?

@poetgrant systemd exists because what came before it was even more terrible in many ways, despite the propaganda, consolekit was unmaintained, each package had their own spaghetti shell script instead of a uniform service file etc.

systemd's far from perfect, but looking at sysvinit with rose tinted glasses doesn't help either.

Follow

@MatejLach @poetgrant OpenRC? Runit? S6? Nobody is arguing that we should go back to sysvinit...

@kungtotte @poetgrant None of these solve the problems I have with sysvinit, they're part of the same philosophy.

Plus, none of these are willing to maintain their own replacement for consolekit etc. They're not in the same league as systemd.

Sign in to participate in the conversation
Fosstodon

Fosstodon is a Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.