... like the fact that drivers don't work because they artificially bumped the NT version from NT 6.3 to NT 10, even though Windows 10 is very much NT 6.3, like NT 6.2 is 8/2012, 6.1 is 7/2008 and 6.0 is Vista. Sometimes I can modify the INF file and trick a driver, all but video (which requires NT 6.x revision-specific).
Microsoft also massively screwed up the GUI code, with all sorts of issues and artifacts that still persist a year later. They have done this with every release since Vista, re-writing the Windows Graphics Foundation (WGF) code, and it's often at odds with the Graphical Display Interface (GDI) legacy. The fact that Windows 10 originally had a 511 entry limit in its menus -- unique to Windows 10, and not in any Windows version prior -- was proof! It wasn't the underlying OS, as StarDock's Start10 didn't have the issue, but shotty development done by Microsoft outsourcing.
All the meanwhile Microsoft still ships some bitmaps in Windows, instead of vector graphics, and they look like crap at 125-150% scaling, several are totally crap at 4K (and even 2.5K) using higher DPI.
I mean, not just Apple in '01+ with Quartz, but even FreeDesktop (Linux) in '03 with Cairo, solved this by going fully vector graphics, and by the mid '00s, both were legacy-bitmap free in most desktop environments. They look 10x better at 4K, yes, even Linux being that every freak'n desktop released in the last 10+ years uses Cario (vector-graphics) based rendering. That's why when you actually see a 1440p (2.5K) or 2160p (4K) Chrome system, it looks very good. Especially since Red Hat, then Google, contracted Ascender to produce metrically compatible fonts in Liberation and Droid, respectively, so even documents are 1:1, while looking better under Quartz and Cario, respectively.
Of course, Microsoft recently deprecated their existing fonts for new ones, and continues to go well of ISO Office OpenXML 2008 spec with yet it's 4th "transitional" format -- yes, 4 non-standard, non-documented XML versions for MS Office now. So compatibility will continue to suffer, even from Windows to Windows system (don't get me started -- there's a reason why Boeing helped sponsor OpenOffice.org XML at OASIS, later ODF at ISO).
I just set Xft.dpi 200dpi (/etc/X11/Xresources) on my
"low memory footprint" LXDE desktops and it just destroys even Windows 10 in looks on my 28" 4K monitor. If I want GL-accelerated, I have many options, from GL/Compiz (GNOME MATE) to AIGLX/Clutter (GNOME Shell) and GL/AIGLX rendering is literally 5x faster/lower overhead than WGF.
But this is what you get in the Microsoft world ... outsourced development so the same people who developed WGF for Vista have had to re-invent it for 8 and now 10. Heck, they had to hire contractors to "reverse engineer" Windows XP hidden calls so Windows 7 was massively improved from Vista, but they've slipped since. Even on the Server end, they keep re-writing the deployment solution, to the point they've changed it no less than 4 times since Windows Server 2003. I mean, even Red Hat hasn't changed their deployment model since the late '90s, but that's what you get when you strongly package software so it's deployable.
The old argument that open source developers aren't as good as commercial developers has utterly flipped. I.e., you have open source developers who stick around a long time, or at least mentor replacements when they move on and are still reachable, while Microsoft extensively uses, and then lets go, contractors. Hence why most of their core architects left for Google and elsewhere by the mid '00s.
