3 ms·
> As an OWNER of the system I should have complete control over what updates I do and don't receive I understand (and share) this sentiment, but you have to un
by smacktoward 11y ago
> As an OWNER of the system I should have complete control over what updates I do and don't receive
I understand (and share) this sentiment, but you have to understand that it's a sentiment that's held by a very very very small number of people. Most people see micromanaging updates as an unwelcome burden and simply don't want to deal with it. So if the only options you present them are "micromanage updates" and "install no updates," they will just choose "install no updates" and roll merrily along with their increasingly insecure systems.
They just don't care, and no amount of nagging from well-meaning nerds like you and I ever going to make them care. For a lot of them, not even getting hacked will make them care. So the only way to protect these people from the consequences of their apathy is to just install the updates for them. This annoys people like us who actually care about this stuff, but since there are so many who don't it's the only responsible approach.
- Retra 11y agoThose aren't the only choices though. The objection is that you shouldn't force people to use auto-updates, because it impedes their ability to use their software. Let's say I'm writing software for something important with a deadline, and my OS decides to update itself and break some of the libraries I was using. That would be completely unacceptable. It's almost no worse than walking up to my computer and smashing it to pieces. You have to be able to control updates because that's the only way to ensure your system is stable. It may not be secure, but stability is often more important than security, especially during critical periods. Most people want their computers to work today the same way it worked yesterday. If updates didn't break things, nobody would have any reason not to get them. But updates are destructive.