> Wrong. For people who disabled Cortana, it kept re-enabling itself automatically after updates. I think that problem is mostly gone now, but it was definitely an issue all the way up till earlier this year.
I'm pretty sure this only applies if you disabled it through the UWP configurator applet. I vaguely remember this happening to me once. I disabled Cortana in group policy or the registry editor and it never happened again. And you're undermining your own argument by admitting that the problem doesn't actually exist anymore anyway...
> The article has one tiny line-item about fragmentation and it was about architecture. I agree that it's not an issue for most people, but OP is making a comment about a design problem. You are mis-representing the argument by talking past it.
The article's brief mention of fragmentation issues was wrong. It doesn't get a pass just because it was a brief mention. A huge list of issues looks impressive until someone breaks it down and points out how many of the issues aren't valid.
I have no idea what you mean by "architecture" or "design problem." The article claimed that disk fragmentation is an issue, and it's not.
> When Windows 10 first came out there were a TON of devices, including very popular printers and scanners, which had no support.
This was a big issue with Vista, but much less so with 10. Even at its absolute worst, Windows 10 was vastly better than Linux for driver support on the desktop. MacOS doesn't really count because of all their first-party hardware. If there's no superior alternative I don't see a valid point against Windows here.
> when the author wrote this, it was true. He should probably update the site.
Oh... I was assuming it was just published since there's no date in parens in the HN story title. I felt like the article was being disingenuous in repeatedly mentioning old issues that have since been fixed, but if the article is older then that changes a lot.