The only downside of switching is systemd is a mess, and getting kinda creepy with captain TechBro running things, think I’ll be headed to a ditro hop for OpenRC or an older init based setup.
I’ve been using Linux since like October and I barely have a grasp on what systemd even is. I only know that my WSL Ubuntu at work doesn’t have it as some sort of security measure. Security against what, I can’t say. But somehow it makes it so that I have to say “service docker start” instead of “systemctl start docker”
Yup, basically. Systemd is “the first program” that runs, and then its job is to start all the other programs that make up a modern computer, most of which run in the background and a user will never see. It’s not the only such “init program”, though, and some people are grumpy that it does too much itself, rather than simply starting other programs to do those things.
But unless you’re involved in starting and stopping background processes, you can’t really tell which one you’ve got. Users aren’t “meant” to care which process was the one that started the power management daemon, or whatever.
The only downside of switching is systemd is a mess, and getting kinda creepy with captain TechBro running things, think I’ll be headed to a ditro hop for OpenRC or an older init based setup.
I don’t think “most users” care about systemd’s design philosophy. Feels a little xkcd 2501
I hope they care about how it’s pushing age verification, at least. It’s not just the departure from core principles, anymore.
I’ve been using Linux since like October and I barely have a grasp on what systemd even is. I only know that my WSL Ubuntu at work doesn’t have it as some sort of security measure. Security against what, I can’t say. But somehow it makes it so that I have to say “service docker start” instead of “systemctl start docker”
Yup, basically. Systemd is “the first program” that runs, and then its job is to start all the other programs that make up a modern computer, most of which run in the background and a user will never see. It’s not the only such “init program”, though, and some people are grumpy that it does too much itself, rather than simply starting other programs to do those things.
But unless you’re involved in starting and stopping background processes, you can’t really tell which one you’ve got. Users aren’t “meant” to care which process was the one that started the power management daemon, or whatever.