this post was submitted on 25 Oct 2026
371 points (95.1% liked)
Programmer Humor
33844 readers
1822 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Systemd solves a very important problem that was defined extremely well.
It also solves it badly, and solved a whole lot of other badly defined problems that it shouldn't.
This is my argument. Do init. Don't pull in literally everything else because you think you know better, like system logging.
Init needs to do system logging when you want to collect it from the daemons stdout, which is the logical place to collect it from. Havin apps handle their own log files is a bad time at best and dangerous at worst.
You are correct ,but again you can just send it to syslog. Just one example of the overwhelming scope creep of systemd.