> Very much disagree. If you pay attention at all to security you'll always hear stories of that one client who hasn't done security updates in 3 months (or 3 days) and gets taken out by the inevitable "exploit Wednesday" shenanigans.
And if you read past the headline you find out that they had numerous other problems with their security practices that were actually responsible for them being compromised, because if "keep it up to date" is the extent of your security policy then you don't have a security policy. There are always exploitable issues in an OS, sometimes updates even introduce them (remember heartbleed? or that time Debian broke key gen?).
> From my experience as someone who has had 0 problems since beta
From your experience as someone with no experience dealing with issues caused by Windows Update, got it.
> Choose any other OS. Any OS at all that is sufficiently complicated as to compete with Windows (maybe as a starting point anything a tiny bit more complicated than ChromeOS). Then name a problem that's happened with Windows 10. I'll show something similar if not worse happening on the other OS you've chosen.
This doesn't mean that Windows 10 isn't bad, it just means that everything is bad.
> The problem, IMO, isn't the OS. It's the freedom the OS allows and the billions of different configurations you'll find out there.
The problem is the OS. If you have designed your OS in such a way as to make updating it a pain in the ass that's prone to breaking things, and turning updates off also a pain in the ass, then the problem is the OS.