Unfortunately, the realities of modern software development make it very difficult to separate feature patches from security patches. Maintaining an ever-increa

Unfortunately, the realities of modern software development make it very difficult to separate feature patches from security patches. Maintaining an ever-increasing number of older versions of the same software indefinitely just isn't feasible. "Bother the user with a dialog that lets them shoot themselves in the foot every time there's an update." isn't a good solution to that problem. Firefox's Extended Support Release[1] is a better one, but even with that users will need to accept a feature update eventually. There may be legitimate situations where it does make sense to turn off automatic updates (that's why the option is there), but they're very niche and require a lot of expertise to pull off without compromising security. Well designed software should intentionally make it hard to disable critical security features without knowing what you're doing. I also don't think informing users about the contents of an update usually meets the bar where it is "absolutely necessary" to interrupt them just for that. Unless your update is about to break something important (which you should certainly avoid if at all possible) patch notes shouldn't be required reading. [1]: https://www.mozilla.org/en-US/firefox/enterprise/ https://www.mozilla.org/en-US/firefox/enterprise/