Windows is a very complex system. Not necessarily because it needs to be complex, but rather because of "wouldn't it be great if we could also..." thinking. Take the registry. Good idea in its core, a centralized repository for all configuration files. Great. But wouldn't it be nice if we could also store some states in there? And we could put the device database in there, too. And how about the security settings? And...
And eventually you had the mess you have now, where we're again putting configuration files into the %appdata% directory. But when we have configuration in there already anyway, couldn't we... and we could sync this for roaming, ya know...
Which is the second MS disease. How many users actually need roaming? 2, maybe 3 out of 10? The rest is working on a stationary desktop, never moving, never roaming. But they have to have this feature, needed or not. And if you take a look through the services, you'll notice that a lot of services that you simply know you don't need MUST run because the OS needs them for some freakish reason. Because of "wouldn't it be great if this service did also...".
systemd now brought this to the Linux world. Yes, it can do a lot. But unfortunately it does so, whether you need it or not. And it requires you to take these "features" into account when configuring it, even if you have exactly zero use for them and wouldn't potentially not even know just wtf they're supposed to do.
systemd is as overengineered as many Windows components. And thus of course as error prone. And while it can make things more manageable for huge systems, everything becomes more convoluted and complicated for anyone that has no use for these "wouldn't it be great if it also..." features.
-It's not systemd versus sysv, it's systemd vs. sysv/syslog/cron/at/user session management. That's a whole lot of potential controversy to take on for a project that you either adopt as a distro or you don't, without good
This reminds me that not all that people experience is systemd's fault. Here the analogy would be dconf.
Ironically, the windows registry is given a *more* filesystem like presentation in powershell than dconf is given by anything. It's exceptionally weird that the platform where 'everything is a file' has drifted away from that philosophy and Microsoft drifted a bit closer to it (though it seemed only temporary, they were talking about a lot of PSDrives, and they seemed to have dropped that..)/
systemd is as overengineered as many Windows components.
I think you mean "overcomplicated". Things that are overengineered are typically robust and reliable. Like the Mercedes 300D automobile (ever looked at one of those engines? zoink! no wonder they have an expected lifetime of 1M kilometers).
I'm running Fedora 26 and... it is no longer robust and reliable. Whether that's systemd or something else, I'm starting to think about jumping ship after having been a RedHat / Fedora user for something over 20 years. I don't typically delve into inits and log files
The road to ruin is always in good repair, and the travellers pay the
expense of it.
-- Josh Billings
Systemd moved Linux closer to Windows (Score:5, Interesting)
Windows is a very complex system. Not necessarily because it needs to be complex, but rather because of "wouldn't it be great if we could also..." thinking. Take the registry. Good idea in its core, a centralized repository for all configuration files. Great. But wouldn't it be nice if we could also store some states in there? And we could put the device database in there, too. And how about the security settings? And ...
And eventually you had the mess you have now, where we're again putting configuration files into the %appdata% directory. But when we have configuration in there already anyway, couldn't we... and we could sync this for roaming, ya know...
Which is the second MS disease. How many users actually need roaming? 2, maybe 3 out of 10? The rest is working on a stationary desktop, never moving, never roaming. But they have to have this feature, needed or not. And if you take a look through the services, you'll notice that a lot of services that you simply know you don't need MUST run because the OS needs them for some freakish reason. Because of "wouldn't it be great if this service did also...".
systemd now brought this to the Linux world. Yes, it can do a lot. But unfortunately it does so, whether you need it or not. And it requires you to take these "features" into account when configuring it, even if you have exactly zero use for them and wouldn't potentially not even know just wtf they're supposed to do.
systemd is as overengineered as many Windows components. And thus of course as error prone. And while it can make things more manageable for huge systems, everything becomes more convoluted and complicated for anyone that has no use for these "wouldn't it be great if it also..." features.
Re: (Score:2)
-It's not systemd versus sysv, it's systemd vs. sysv/syslog/cron/at/user session management. That's a whole lot of potential controversy to take on for a project that you either adopt as a distro or you don't, without good
This reminds me that not all that people experience is systemd's fault. Here the analogy would be dconf.
Ironically, the windows registry is given a *more* filesystem like presentation in powershell than dconf is given by anything. It's exceptionally weird that the platform where 'everything is a file' has drifted away from that philosophy and Microsoft drifted a bit closer to it (though it seemed only temporary, they were talking about a lot of PSDrives, and they seemed to have dropped that..)/
Of course e
Re: (Score:2)
systemd is as overengineered as many Windows components.
I think you mean "overcomplicated". Things that are overengineered are typically robust and reliable. Like the Mercedes 300D automobile (ever looked at one of those engines? zoink! no wonder they have an expected lifetime of 1M kilometers).
I'm running Fedora 26 and ... it is no longer robust and reliable. Whether that's systemd or something else, I'm starting to think about jumping ship after having been a RedHat / Fedora user for something over 20 years. I don't typically delve into inits and log files