Microsoft's own operating system should finally start working on its own hardware ... 'in the coming weeks' Lurking within the epic patch dump offloaded on Windows 10 2004 users last night came the news that Surface Pro 7 and Surface Laptop 3 owners have been waiting for: fixes for glitches. The unexpected restarts and errors afflicting Always On, Always Connected devices have been rectified as part of KB4557957. Not that the …
They really do need to hire another tester. They can afford it...
Their own hardware is clearly so expensive that they think it would be an unnecessary luxury to allow their tester(s) to use it ... if the testing department's budget is that small they probably can't afford another (any?) tester.
You would think either the Windows team or the Surface team would be responsible for validating new Windows builds on Surface hardware.
Maybe there was a big childish argument inside of Microsoft because neither of them wanted to do it, so now nobody does it.
Still striving to get the os running well and reliably on ANY hardware and still trying to get their own office products to work with their os and their other products! They couldn't integrate a cock with an arse! End users generally don't need more than a Chromebook and it offers a great user experience and is easily maintained. Be brave!
When they send out a new Windows build and it fails out in the wild on some specific hardware combination they've not tested, I think any reasonable person can accept that as very difficult to avoid. But when MS don't even bother to validate builds on their own hardware prior to release, it just goes to show how broken their processes are.
I also get the feeling that they're losing control of the Windows codebase. Reading through the list of known issues makes you wonder why so much stuff is getting broken on releases that on the face of it don't really deliver very much. They must be spending more engineering effort refactoring low level code than actually changing things that would benefit users.
Because the code is not fully developed for that hardware (call it shit of you prefer) and won't support that particular device.
Why that happens in the wild is different question, however I think 'shit' remains the answer.
There is always going to be an unusual combination of hardware/software that gives a problem but MS not getting it right for their own expensive hardware is something they should not have allowed to happen.
Once upon a time Microsoft was TWO companies : Windows and Office.
Windows made some kind of OS while Office made Office software for Steve Jobs and his gang.
Now Microsoft ALSO includes a cloud company ( Azure ) and a hardware company ( Surface ).
If anything Surface learned Windows quickISH.
There must be people inside of Microsoft looking at the shit the Windows team keep releasing, and wondering why they don't get working on a Linux distro.
I would suggest the distro could have a Windows-like UI that people would prefer to Gnome or KDE, but I'd much rather have Gnome than something that looks like Windows 10.
I look forward to the Linux distro from MS as I can see 2 possible outcomes.
Either it will be as bad as windows 10 and the current crop of releases from M$ and it will need a community that isn't there to fix it. It will flounder about and show that they really can't do an OS, even with the support of all those communities. Communities made up of hobbyists who throw out distros all over the place - unlike the fully paid and skilled developers in Redmond.
Or it will be brilliant and look amazing, which means everyone will look at it and go - "So why isn't windows 10 just as amazing?"
Can't wait.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
