140
Is Systemd that bad afterall?
(sopuli.xyz)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
No, it's not bad.
tbh, I've always like Apple's launchd.
Getting a "control center" for your init, with user groups, modularity, memory limits and queryable status/control is great. (Sometime people forget how painful init scripts can be...)
The only problem I see is the tendency to cram everything into systemd.
I absolutely agree with you, but not quite on the las point. SystemD is modular, right? I can still pick and choose something else for tasks that SystemD handles. Also, it might be a good idea anyways to centralize some common tools for distros and devote developer ressources somewhere more specific and necessary.
It'll always be an open field of software stacks to choose from, but having one big, featureful and solid base stack for most usecases seems like a win to me. It's all completely FOSS anyway, it's not like we are risking a vendor lock-in here.
It often feels like people only complain about things because they are not used to them