this post was submitted on 22 Apr 2024
516 points (97.3% liked)
linuxmemes
21410 readers
811 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think that's true at all. I'm ok with systemd, but I don't really like it, and find much of the criticism valid. At this point the reason I use it, and am more-or-less fine with it, is that it has become the de facto standard and is very well supported.
Which is also one of the reasons I dislike it
it is such an integral part of modern Linux systems that it can be hard to change, which reduces a lot of the appeal of Linux
flexibility and freedom.
I'm fine with systemd, but I really do get the feeling that it exists more because of Red Hat's NIH syndrome than anything that was actually bad about upstart.
Nah, upstart actually sucked. I used it in an embedded project and getting things to start consistently was a nightmare. We had to put all kinds of sleeps in because there was no way to tell when something actually started, only when it was told to start (i.e.
start on started x
would start both at essentially the same time).With systemd, that all went away. It magics away sockets and whatnot so things just work properly. Also, our startup time went way down because things could start just a bit earlier, and the config files were more intuitive.
Upstart was a poor solution in search of a problem, and items sysvinit was honestly better imo because sysvinit didn't hide little gotchas all over the place. Systemd is an over engineered solution to a real problem, but it works really well. Oh, and socket activation is magical.
That said, I still prefer the FreeBSD way, which is just a slightly fancy sysvinit. It works well, though it won't win any awards for fanciness. Maybe launchd, if it ever comes to FreeBSD (maybe it has? I've been OOTL since 12), will be cool, IDK.
On the other hand, fragmentation makes software hard to support all of them. It seems like a dilemma.