For a desktop it's suitable for 99% of what you'd want to do. Might not be the best tool for large servers or something (I really don't know) but I'm sure all that depends on use case.
this post was submitted on 04 Oct 2023
727 points (95.2% liked)
linuxmemes
21378 readers
1146 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
sudoin 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
I feel like, at this point, it has more than proved itself as a general purpose desktop scheduler. But there are situations where you would want something different but a lot of software depends on it anyway.
I also kinda don't understand the hate toward the project itself, other than hearing some of the technical guidance on it has been a bit arrogant in the past or something. Sounds like sily open source drama to me honestly.
The arguments against systemd come from the same people that love IRC, mailinglists, tiling window managers, split keyboards, don't have a mouse, debug with printf, main arch or gentoo, unironically write RTFM|LMGTFY, call users "lusers", play DnD, think Startrek and/or Star Wars cannot be topped, identify with the portrayed super hackers in media, and are proud of doing things the hard way just to feel some kind of superiority in their life.
Edit: for those who don't get it, I'm obviously not being serious. If you fit this mythical, stereotypical person... uh... good job?
Well, I like IRC, ergonomic keyboards, sometimes debug using print commands, use Gentoo (Happy birthday!), play DnD and sometimes have to do things the hard way, and I like systemd, especially as a developer, I can test services right from my user account.
I think the hate comes from people who just want something to hate.
load more comments
(1 replies)
This description literally fits everyone in my team at work and i love it. I m the least nerdy one there and its beautiful.
load more comments
(16 replies)
I only hate it because I can't figure out how to run a blocking script before everything else when a suspend is initiated.
load more comments
(4 replies)
Linux power-users hate it when a tool tries to become a platform.
It breaks the principle of single responsibility and becomes a threat to the evolution of alternatives.
It's pros and cons. Having a platform is better because everyone works together on a single effort. But it also becomes a risk because now everyone depends on a single thing that does too much.
I can't agree with this comment more.
A lot of Unix philosophy, at least in the early days, was KISS. Keep it simple stupid.
Lots of interlocking components, doing one thing, doing it well.
Systemd turns that philosophy on its head.
What else are you going to do? runnit? 😭
It's a pretty bridge, they'd say, but be careful you don't look at the supports. It was built using bad techniques, bad procedures, no coordination and no inspection.
Just cross your fingers as you drive over and hope it doesn't blow up because of its flawed construction.
I find it's a great way to cross the river, today.
load more comments
(1 replies)
I find everything so complicated with systemd.
SysV was just intuitive for me and my knowledge. There was just one directory with all the startup scripts in it. And they were run in their alphanumerical ordner. Just that simple. If I wanted to change the order in which the scripts started, I just had to rename the file. You don't want a script to run at all? Just remove it.
I assume, systemd has many advantages for a knowledged user. But for me, it still is just a hassle.
I haven't had to debug a bash script since systemd became a thing, so I have a vastly different experience from you.
load more comments
(2 replies)
And what happened if one of those scripts failed?
How did your express a dependency of a service on data being mounted?
Did you ever have to face debugging failing networking via scripts?
load more comments
(1 replies)
load more comments
(1 replies)
Every new tools (especially those being pushed by big corporations) meets resistance and suspicion. It's a new thing to learn instead of something proven to work, usually more resource-hungry...