| >It is true that it's a security risk, but instead of forcing something that people clearly do not want, why not make something that they do want. Make a product they want to upgrade to. Two things. First, people want their computers to be secure. Most users do not seem to understand that keeping your system patched is a prerequisite to remaining secure, and those people have to be dragged kicking and screaming into running updates, which is why Windows 10 has gotten so aggressive about enforcing it. If someone gets exploited through a hole in Windows, it comes back to haunt MS; they learned that well and good in the Windows 98 days, and they learned that users will never install updates without being forced to do so in the XP days. Second, the kind of people who are afraid to install security patches cannot be enticed by any new program or UI modification. They have an defensive dislike of computers. They just want it to stay the same forever, and even if you release new versions that are identical at the UI level, people still won't upgrade to them because they're afraid it'll "break shit", as you succinctly put it. End users may not like MS's aggression about updates but it is actually sensible for 99% of the userbase out there. MS's problems are unique among desktop OS vendors because of the wide and varied audience that relies on them to provide a good general-purpose OS. It's reasonable that power users would resent MS's update policies, but MS does not have the luxury of tuning their release policy for the power user. Power users should be using not-Windows. |
Except that even power users like having large libraries of available software, including things that may not be available on "not-Windows".
I'm fine with aggressive defaults and sensible settings for the 99%, but I'm accustomed to being able to disable things that cause me problems or get in the way of doing what I want to do. If a system doesn't get out of my way, it's possible for it to become more of an impediment than a tool.