As a user of software, I couldn't agree more with the OP that automatic updates:
> should always keep the user centric
> should be incremental and security or bug fixes only
> should never update a user interface without allowing the previous one to be used as the default
> should never be used to install telemetry or spyware or to re-enable it if it was previously switched off
> should never be used to install other software packages without the users explicit consent and knowledge
> should never change the format of data already stored on the system
> should never cause a system to become unusable or unstable
> must allow a revert to the previous situation
> must be disablable, in an easy and consistent manner for instance on mobile devices
> should never cause the system to become inaccessible or restarted without user consent
> should always be signed by the vendor to ensure that the update mechanism does not become a malware vector
> should never cause commercial messages or other fluff to be included
> should never cause configuration details to be lost
> should always be backwards compatible with previous plug-ins or other third party add ons
I agree: Software vendors "should" and "must" do all these things when updating software on my computer without my permission.
But often they will NOT, because their economic incentives are frequently stacked AGAINST it.
For them, it's often cheaper or more profitable in the short run not to do any of these things.
> should always keep the user centric
> should be incremental and security or bug fixes only
> should never update a user interface without allowing the previous one to be used as the default
> should never be used to install telemetry or spyware or to re-enable it if it was previously switched off
> should never be used to install other software packages without the users explicit consent and knowledge
> should never change the format of data already stored on the system
> should never cause a system to become unusable or unstable
> must allow a revert to the previous situation
> must be disablable, in an easy and consistent manner for instance on mobile devices
> should never cause the system to become inaccessible or restarted without user consent
> should always be signed by the vendor to ensure that the update mechanism does not become a malware vector
> should never cause commercial messages or other fluff to be included
> should never cause configuration details to be lost
> should always be backwards compatible with previous plug-ins or other third party add ons
I agree: Software vendors "should" and "must" do all these things when updating software on my computer without my permission.
But often they will NOT, because their economic incentives are frequently stacked AGAINST it.
For them, it's often cheaper or more profitable in the short run not to do any of these things.