• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 9 Launch

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
What's the point of daily updates? Both Windows and OSX have System Updates that don't require any subscription nonsense. I wouldn't want to waste time every day updating my OS- just if something actually requires it every now and then.

Daily updates give you the best software and security immediately, instead of waiting until x number of features accumulates to warrant a release. Windows and OSX don't upgrade core features. You get security patches, and occasionally some minor features. To do a rolling release with them would require a subscription. Otherwise, one copy of the software would be sold, and it would be good forever. Update time? I spend about 2 minutes a day updating my machine, and that includes reading any bug reports that may be relevant. I spend less time updating my entire system than most people spend trying to figure out how to use Google :^D
 
There is a very big difference between a bug that renders web page not exactly to W3C standards and a bug that trashes your hard drive or operating system making you waste couple of days to rebuild the system and restore the data. Agile mindset has no place in system critical applications such as OS.

Problem #1: The assumption that Agile forces bad updates. Total nonsense.

I'd much rather see small, incremental updates every 3-4 months than one giant service pack every 1-2 years that introduces so many bugs that the first month post release is miserable until they release 10-20 patches to fix the fixes.
 
Daily updates give you the best software and security immediately,
It can also possibly introduce bugs with each update. And I totally disagree about 'the best software'. For 3rd party developers, the OS updating daily must be like chasing a moving target. Who's to say tomorrow's OS update doesn't break something or cause instability in todays application update? There may be some advantages to such frequent updates, but I wouldn't argue that better software was one of them.

Also, I'm curious, what happens if you leave a system off for a few weeks (or pick any length of time) and then come back to update it, having missed however many daily updates? Is there a logical rollup of previous critical updates and possible broken dependency issues, or can you just start updating from the latest daily without it mattering how many you missed?

Windows and OSX don't upgrade core features.
OSX certainly updates core features, just with logical 10.x.x point updates.

You get security patches, and occasionally some minor features.
Which is all that's needed.

To do a rolling release with them would require a subscription.
That's not exactly a selling point for rolling releases then.

You spend two minutes a day updating your systems- I spend zero minutes a day updating my systems. Bottom line: if things work and are stable, then that's all that matters.



Problem #1: The assumption that Agile forces bad updates. Total nonsense.

I'd much rather see small, incremental updates every 3-4 months than one giant service pack every 1-2 years that introduces so many bugs that the first month post release is miserable until they release 10-20 patches to fix the fixes.
The incremental update process you're describing is exactly how point updates work.

Windows service packs (and Mac Combo updates) are really just a roll-up of previous updates, not a whole collection of new untested updates. I don't recall any MS service pack (or Mac Combo update) that was a PITA for a month before being patched constantly like you describe. Or was there a specific such update you're referring to?
 
Last edited:
Also, I'm curious, what happens if you leave a system off for a few weeks (or pick any length of time) and then come back to update it, having missed however many daily updates? Is there a logical rollup of previous critical updates and possible broken dependency issues, or can you just start updating from the latest daily without it mattering how many you missed?

I can go months between updates, and it only means a longer download to catch up. I've heard some systems get bitchy if you let them go too long, but that just means they need better dependency resolution.
 
I don't recall any MS service pack (or Mac Combo update) that was a PITA for a month before being patched constantly like you describe. Or was there a specific such update you're referring to?

Vista SP1 would be the best example I could recall. It included some changes to the overall OS as well as some new features, and it crashed and burned early on. I seem to recall XP SP1 or 2 having some early problems as well, but that's 10 years in the past now so my recollection may not be spot on there.

Probably irrelevant now though since it does seem like point updates are the future for MS. Now they just need to do a yearly conference where they demo the point update as if it will revolutionize the industry 😉.
 
I love 8.1 preview so far. so I suspect 9 will be awesome. Today I got the WIndows 8 tweaks at the bookstore, has a lot of nice advanced configurations I never knew about.
 
I like Win 8, but even love Win 8.1 more. I'm running it (8.1 preview X64 Enterprise ver) on my 4 year old C2D notebook and on my sig system and couldn't be more happy with the speed of boot up and shut down. The only two issues I have had are: 1. McDonalds Monopoly site would work in IE and 2. I'm waiting for Norton to make NIS compatible with 8.1.
 
Windows 8. and now windows 9.next what they going to do is invert those number.then back to stone age (98) lol
 
Back
Top