Linked by Thom Holwerda on Fri 30th Nov 2012 11:55 UTC
Windows I'm back from my vacation to the US, the jetlag has mostly passed, so back to OSNews it is! So, Windows 8 has been out for only a little while, and we're already moving on to the next 'version' of Windows. Version is between quotation marks, because unlike previous releases, this doesn't appear to be the a monolithic single release. Instead, Windows Blue, as it's currently codenamed, is more of a procedural change than a technical change: Windows is moving to yearly releases for all devices - PC, tablet, phone.
Permalink for comment 543705
To read all comments associated with this story, please click here.
RE[2]: Or could it be
by Laurence on Fri 30th Nov 2012 16:18 UTC in reply to "RE: Or could it be"
Member since:

He does have a point.

Windows Update is pretty poor as update managers go by:

* no proper foresight with dependency resolution. So instead of just jumping to the end and pulling all the latest patches, it has to run through every update incrementally. This often means that you need to reboot after some core updates before the next increment of core updates can be performed.

* too many core systems that cannot be independently restarted. I'm by no means saying that Linux is perfect, but I love the fact that the only updates that need a reboot are kernel updates. Everything else can be independently unloaded and reloaded.

* annoying forced reboot cycles. If an update happens that needs a reboot, you get a 15 minute (IIRC) warning and that cannot be cancelled, only postponed for a few hours. Worse yet, if you happen to be away from your PC during that tim (eg making dinner) then you may find that Windows has forcefully rebooted your system.

While most of those points I can forgive because of various architecture decisions within Windows; mean a fix would be more work and potentially more dangerous than the annoyance of the current set up. But the last point is pretty unforgivable in my opinion. There should be no circumstances where the OS is allowed to reboot an unattended PC; that's an administrator / end user responsibility alone. And the example the aforementioned commenter raised was just one of many great reasons why an unattended PC shouldn't be assumed safe for system reboots.

Reply Parent Score: 6