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 There are two things I don't understand:

1) Migration from init to systemd
2) Migration from ifconfig and netstat to ip shit.

I'd love to hear an explanation of both of them. Even a theoretical one, I don't really care. Just something.


@ekaitz_zarraga that is something I am unsure about myself. I think I know why the Linux community migrated to systemd, because it hands over the reins of responsibility to someone else. Makes life easier, but I am starting to think that the costs heavily outweigh the benefits. As for point 2, I have no idea... the old way works fine, even to this day... heck, I'd say the old saying is right, 'if it ain't broke don't completely write something new with tons of new bugs.'

The cost was outweighing its benefits the second they migrated to it. Are there any benefits at all?

Sign in to participate in the conversation

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