The_Great_Sephiroth
Refugee
Ditto, I started managing them in 2001, specifically shell-only servers back then. Normally it isn't too bad to figure out something, but when you start adding layers of complexity where this depends on that and that depends on the other, it gets annoying fast. Another reason to avoid systemd. I have done simple updates, rebooted, and something critical is down. It's not that the software is bad, but now I need to do configuration changes or something because that was changed for security/speed/stability/whatever and my current config no longer works. It could be worse. Linux sometimes breaks things just like Windows, only Windows 10 tends to break things often.These conversations tend to end up in flame wars which I'm not going to let happen so this is the last time I'm going to comment on this.
I've managed Linux systems for 20 years. It's only a matter of time until you install something and things are going to quit working on you. Then you need to know how scripts work and how to use an editor and a bunch of other things that normal people who don't know anything about operating systems or programming or script writing don't know just to understand what the hell is going on much less how to fix it.
This is just fine if that's what you want to do. But don't switch to unix thinking it's better than windows and you're going to have a better experience using it.
The most recent debacle in Linux was the Intel video driver not working right after a specific kernel update. I believe after 5.4 something happened that broke many Intel HD Graphics setups. Fixed now but it was broken for a while.