|
|
|
|
|
|
by inshadows
2233 days ago
|
|
|
Well, to be fair, these user space components are often judged as catastrophes from the point of view of Linux/UNIX users/admins. In other words, Windows components for same tasks were never scrutinized at this level. Windows users used often scoff at me when I am troubleshooting problems with my Linux boxes. But the fact is, I can troubleshoot and in most cases fix problems with systemd/NetworkManager, whereas when corresponding problems arise on Windows boxes there's really not much you can lean on, because inner workings of these components are not public, so 95% of Google searches result in total crap, and the remaining 5% reveal that design of these components isn't at all that perfect. (NetworkManager equivalent in Windows is big pile of steaming crap.) So yeah, I don't like design of systemd. But hell, compared to dealing with Windows, it's precious. |
|
|
I feel like many who level this charge have unfortunately never really looked into its design or compared it realistically to what came before, because I can tell you that if I am comparing the ability to write a systemd service in a declarative way and having it working with the same set of commands across all major distros, I'll take that over having shoddy quality bash scripts that vary across distros just slightly enough to annoy and that rely on a patchwork of PID files that is very easy to mess up, I am taking systemd any day of the week.