Hacker News Reader

Comment by jmclnx | Hacker News Reader

>Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new features.

https://cscie2x.dce.harvard.edu/hw/ch01s06.html

systemd seems to violate this at every turn, but sadly they are not the only ones to do that in Linux. I wonder at what point we should start considering Linux to be its own thing instead of "UN*X like".

View on HN

I know people like to complain, but these comments are not really based in reality. systemd is really a suite of applications that work together to provide init, service management, network management, &c. there's no single giant program that does all this. each component has a specific focused task.

you could break this out into individually named projects, but nobody complains about coreutils enabling dozens of different workflows.

> there's no single giant program that does all this

systemd crown does everything for that to be technically legally right while also making sure that and modern Linux distro is unusable without a bunch of systemd-* projects.

If you don't want systemd, pick a distro that doesn't use systemd. You'll be a lot happier doing that than fighting a distro that has chosen to adopt a set of tools that you dislike.

At this point we're not talking about distros w/o systemd as there are none left speaking from a practical perspective.

We should be discussing management of the metastases, because systemd people still exist and they still want attention and suffering and thus they are still looking for existing AND working tools to destroy.

It kinda sounds like you're upset that the consensus doesn't align with your preferences. (which is the vibe I tend to get from the anti-systemd crowd) Maybe a bunch of y'all should get together and make a linux distro that demonstrates how much better the alternative can be!

I don't think anyone has a problem with dissent, but that energy should be channeled into making something. Complaining about it the comments doesn't write the classic style linux distro that y'all clearly yearn for. Get coding!

See, that's the point. Some problems do not exist and do not require coding.

cron worked just fine for decades until systemd crowd decided to "get coding".

What about problems that are not "one thing" only? Like, should a web browser be 640 piped subprocess in a trenchcoat, would that really be maintainable/easier to see how it works?

Lot of this comes from kernel though, cgroups and processes have tons of knobs to tweak and systemd merely exposes those.

Reply on news.ycombinator.com