The testing Mess of Microsoft

<p>There is a lot to said for Linux's Red Hat / Fedora Model of testing and rolling out new builds. The model I think Microsoft should adopt, and adopt it now. It's almost as though they don't want to adopt the common sense approach just to show MS are doing things differently, when the Linux Red Hat/Fedora model works, and works well.</p><p><br></p><p>The insiders programme does seem to be taking on all the complications of Windows in terms of it's Enterprise licencing options, by that I mean it's a job in itself to understand every nuance.</p><p><br></p><p>If Windows 10 had a simple no-nonsense "Locked Privacy-No Telemetry" Red Hat type model for SMB's, paid for through an "old style" upfront licences, we'd certainly pay for it over the digital licence version, but maybe we're the exception. </p><p><br></p><p>Microsoft have truely forgotten that sometimes "Less is more…" (and people will still happily pay for that, if it fits their needs. MS are almost trying too hard).</p><p><br></p><p>It would need a slower release cycle. It wouldn't have to change, maybe every 3-4 years, and just include the best features from the Windows 10 Insider/Consumer "Conduited User Data to MS" aka Spyware Version, that had bedded down, keeping only the best of those new features, as being useful over time. There is far too much "tooing and froing" at the moment.</p><p><br></p><p>Privacy is key, maybe it's a US free-market thing, but here in European, it's a much bigger issue than MS(US) seems to accept, and there is money to made, in respecting people's Privacy. MS(US) don't seem to have understood that yet. </p><p><br></p><p>Paul Thurrot's stance on Privacy ("don't worry you're little heads approach") is something I really don't agree with. Securing your own data is extremely important. This data is extremely valuable, MS really don't want you switching off all that conduited data to MS – Telemetry. </p><p><br></p><p>The default Defender setting of uploading of user files to MS, because they look suspicious (wishy-washy and open ended in what defines "suspicious"), is just plain wrong.</p><p><br></p><p>———————————–</p><p><br></p><p>Which version to install?</p><p><br></p><p>Windows 1607 Anniversary Editon is pretty good in all fairness (the one I'd currently recommend), works well and is my current default main Windows 10 install. (I use all these in equal measure – Win10,Win7,Linux and MacOS Sierra during my week, Linux is current OS preference, my 'default'). </p><p><br></p><p>I do have 1703 working (minor issues for me), and I've just installed Window 10 Insider Build 16251, which has the People Bar thingy.</p><p><br></p><p>Regarding Build 16251, for the amount of effort to install these feature updates 40mins+ on another machine/SSD, the benefits to the end user are slim on the ground. Yep, lots of behind the scenes changes, but it's mostly rearranging those "thrown Ballmer chairs", i.e. for Joe Bloggs, it's pretty difficult to notice anything different over Win10 1607.</p><p><br></p><p>Biggest Bugbear? </p><p><br></p><p>Windows Explorer – it's still crap (not as bad as Win7 Win Explorer though). No one developing/working on this, works with files day in day out, and it shows.</p><p><br></p><p>Drag and drop needs some serious work. Additonal Selections deselect themselves each time a file is moved/copied across in the background, drives expand as you hover over them, resulting files ending up in the wrong place as you let go to drop them into place. It's too easy to drop files into an already compressed file by mistake, i.e. add it to a zip/rar already in the directory. It's just awlful.</p><p><br></p><p>If I'm working with files, I don't use Windows for that reason, I prefer Linux as my desktop, if I need to work rearranging files, into different directories.</p>