Microsoft lobs Windows 10, Server Oct 2018 update at world (minus file-nuking 'feature') after actually doing some testing Is the Windows October 2018 update here again? Did it ever exist previously? Are we all in a feverish dream where the latest version, build 1809, is stable and fit for purpose, and Patch Tuesday was totally uneventful? Our finger hovers over the "no" button, but we live in hope of someone one day fitted a "yes" key. Huawei …
It is like Ubuntu release names, first two digits are the year and the second two are the month. Although as they withdrew it and then re-issued it should probably be 1811.
Calling it 1811 would show that it wasn't released when they said it would be and that would involve admitting a fault so it is still 1809
1809 is just the public-facing version number (obviously based on the last two digits of the year and the month it was released in). It's just a name plucked from the ether for something specific.
Build numbers have a different significance compared to version numbers, generally.
There are three version numbers. The 10.[randomdecimal] one that doesn't matter, the build number, and the version number. The version number is 1809, even though that's the wrong number (see my post above for why it's wrong if you care which you probably shouldn't). You have the build number, which at least goes in order. So when that number goes up, the build is newer. Build 17134 seems to be the final version of windows 10 version 1803. So in short, it's crazy.
Welcome to the 21st century - I suspect that the Windows sources have become so complex with patches and features added and fixed and re-patched since it's release, that any changes are simple rolling the dice as to what they will break. Does anyone actually understand the whole picture any longer or is it simple one team working against a dozen other feature update teams?
You can evaluate and validate your teams patches and features but when another team rolls out its updates, who checks to see if there are any interactions? That's the user job these days isn't it?
you get a FREE OS, aka W10, and they turn you into a guinea pig and spy on you and sell your data OR
you get a FREE OS, aka Android, and they spy on you and sell your data OR
you get a PAID "obsolete" OS, aka W7, and they spy on you (a little), sell your data (a little) and you tremble in fear, because FUD, OR
none of the above, aka Apple x-thingy and them linuxes, but hell, neither's for mainstream joe (for different reasons).
Apple does spy, somewhat, but nothing like what other companies do. They don't collect as much information, are better at allowing data to stay on the device rather than getting sent to them, and don't make a large part of their business from data exploitation. So yes, I'm saying that.
How many of us on his forum have a "test device" enrolled in the developer previews? I know I do and apart from periodically updating it and having a prod about I literally do nothing on this device. So as far as Microsoft are concerned the data they slup from it is all good?
How many of us on his forum have a "test device" enrolled in the developer previews? I know I do and apart from periodically updating it and having a prod about I literally do nothing on this device. So as far as Microsoft are concerned the data they slup from it is all good?
I have one like that. Other than using it to buy music off of whyTunes (because Apple can't be arsed to make an Android client or make a way to buy directly off the website), or my daughter borrowing it while I'm fixing her laptop, it doesn't do a lot other than letting me see what crap is coming down the line.
I *HAVE* considered the possibility that MS should make an automatic test/validation suite we could run on our TechPreview machines when we're not doing our own "testing" on them. Sure, it's giving them another excuse to continue not doing their own testing, but that's what their going to do anyway.
Looking at the evidence over the last few updates, apparently many/most do their testing in virtual machines rather than real hardware. Thus, where the HAL hits the hardware, this hasn't been tested against the (literal) myriad of systems out there. A monoculture if ever I've seen one.
Were I even using Windows 10, I can see that I might do the same. Instead, my laptop uses Windows Server 2016. First off, it's only used to connect and do things on the Internet, my canary in the coal mine, not just about Windows but what is "Out There" to get my devices. [All other devices are energy-gapped save the tablets. No big deal restoring.] The other reason is that the laptop can't seem to keep a working Windows 10 alive; has no problem doing the same with Server 2016. Same device driver model, supposedly, for both. Go figure why.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
