|
|
|
|
|
by Nextgrid
2222 days ago
|
|
Simple things that used to work fine. Start menu search, for one. The start menu used to be blazing fast and search was consistent. Nowadays the start menu can be sluggish in certain cases and search might not return local results seemingly at random. The calculator used to be fast and load instantly, now it's one of those UWP monsters that even asks you to rate it in the Microsoft store... I don't recall hearing about updates bricking machines or causing data loss at scale back in the Windows 7 days but it seems like that is now a relatively common occurrence, amplified by the fact that you can no longer hide/defer updates on consumer versions of Windows. I think the firing of their QA team and delegating the work to unpaid "insiders" and telemetry might have something to do with this. The new Settings UI is absolutely disgusting both in looks and information density and is a clear downgrade from the previous version. I can go on and on. I would sympathize if they were pushing the boundaries of software engineering but what we're talking about isn't groundbreaking - these are problems that were mostly solved a decade ago and Microsoft intentionally backtracked on their progress by the looks of it. |
|
This could also be explained by user expectations for software rising but quality of Microsoft code remaining constant. In the past users may have written off such events as 'just the way computers work sometimes' but perhaps now users realize that computers needn't be so unreliable.