4 ms·

All these never ending stories with Windows Update in W10 is like walking around the problem that is caused by lack of proper QA team that was pushed onto users

by pndy 6y ago

All these never ending stories with Windows Update in W10 is like walking around the problem that is caused by lack of proper QA team that was pushed onto users and removal of previously perfectly working feature of selective updates installing - which was obviously great because in case of problems user could just skip the bugged patch and wait till a fixed version is released. The old way of delivering patches in Vista/7 style should return - even by a price of patches "weight". I get it: they want people to stay up-to-date to avoid problems of zombie-machines but Windows isn't OSX that works on narrow set of hardware and software configurations - these differ much (duh) and that affects how updates work. Expecting that users will ditch their workflow to report all issues on forums (or these will come from the "enthusiasts" testing grounds), will want to play countless reinstallations, backups and restoring is just wrong. This leads powerusers who want to have more control over their machines to disable (temporarily or permanently) WU along with associated processes which by the way, seem behave in a very malicious way.

rstuart4133 6y ago
Windows updates have another feature: you wake up in the morning, and UI has changed, the feature set has been updated, things can no longer work. This happens on Android as well. Infuriatingly Google Maps decided to update itself during the day, between two car trips. I'm driving on a freeway, realise I don't know where I'm going, and fire up maps to tell it the address and am confronted with a new UI that is going to take some real concentration to decipher, the sort of concentration that can not be given while driving down a freeway. I yelled a few things at the maps developers that day. Compare that to Debian. Updates are backports of bug fixes to the existing source code base. It is the absolute smallest change possible to fix the defect. There are literally 10 of thousands of updated to Debian packages over the life time of a single release, and yet you noticing any change over it's entire lifetime is very unlikely. [0] Calling Debian Stable "stable" is an understatement. It's a rock. Bedrock even. On Debian big changes on happen when you move between versions. Versions are currently supported for 6 years. The timing of moving to a new version is at the compete digression of the user. [0] That's a bit of a lie. Web browsers in particular are so big and complex the manual work of backporting fixes has overwhelmed the Debian Developers. For those packages only, they stick with the closest upstream provides, which is the ESR version for Firefox. But they only last a year or so, which forces Debian to move to a new version occasionally.

by pndy 6y ago

rstuart4133 6y ago

Windows updates have another feature: you wake up in the morning, and UI has changed, the feature set has been updated, things can no longer work. This happens on Android as well. Infuriatingly Google Maps decided to update itself during the day, between two car trips. I'm driving on a freeway, realise I don't know where I'm going, and fire up maps to tell it the address and am confronted with a new UI that is going to take some real concentration to decipher, the sort of concentration that can not be given while driving down a freeway. I yelled a few things at the maps developers that day. Compare that to Debian. Updates are backports of bug fixes to the existing source code base. It is the absolute smallest change possible to fix the defect. There are literally 10 of thousands of updated to Debian packages over the life time of a single release, and yet you noticing any change over it's entire lifetime is very unlikely. [0] Calling Debian Stable "stable" is an understatement. It's a rock. Bedrock even. On Debian big changes on happen when you move between versions. Versions are currently supported for 6 years. The timing of moving to a new version is at the compete digression of the user. [0] That's a bit of a lie. Web browsers in particular are so big and complex the manual work of backporting fixes has overwhelmed the Debian Developers. For those packages only, they stick with the closest upstream provides, which is the ESR version for Firefox. But they only last a year or so, which forces Debian to move to a new version occasionally.