3 ms·
Perhaps the issue with systemd is not technical superiority nor convenience, as many commenters routinely present it. Perhaps the issue is actually user contro
by 1vuio0pswjnm7 3y ago
Perhaps the issue with systemd is not technical superiority nor convenience, as many commenters routinely present it.
Perhaps the issue is actually user control.
Personally, I know that if I followed the philosophy of always picking the solutions that were the most technically superior, the easiest to use and/or the most convenient, I would have far less control over the computers I own. YMMV.
For the avoidance of doubt, the term "control" as used here refers to the ability of the user to control systemd and thereby control the computer, not the ability of systemd to control the computer. The later might be "technically superior" to prior alternatives.
- qbasic_forever 3y agoSystemd doesn't remove any control, and in fact gives a lot of extra control over things like process dependencies, environment, etc. The big complaint people had/have really just boils down to someone moved the cheese--your bespoke and brittle startup scripts are now declarative config files. Some people had to learn something new and that _really_ angered them.