Because that isn't the typical experience. For a start, the guy gets into driver parameters, testing kernels, and compiling from git. None of that is typical at all, hence why the Ubuntu etc. installation instructions say nothing about that. All a newbie user would know would be that some of his hardware isn't picked up in one particular distro. Maybe some older kernels work - who knows, did they test? What about the kernels in a STABLE version of a Linux distro that's aimed at first-time users? Did that work? I'm guessing you have no answer because you haven't tried.
(And, most importantly here, if that person was you, DID YOU REPORT THE BUGS? No? Thanks a lot for smearing bad news across the Internet without even giving people a chance to fix it).
However, it's like comparing my latest foray into IBM BladeCenter servers. On boot from a standard Windows 2012R2 install disk, they crash. That's it. BSOD and end of game. With a 10-minute BIOS boot, it doesn't matter how long you try, it still just crashes before it gets into Windows.
You have to create the support DVD from IBM-supplied drivers yourself. They don't supply one. This involves several HOURS of downloading, lots of disk space and knowing exactly what components you have in your blade server. Down to the difference between an HS23 (1506) blade and an HS23 (8883) blade, for example.
Then you have to burn that to a DVD (because it's too large for CD). Boot EVERY blade from that one by one, which runs off and updates 20-30 items of firmware on the blades and server and RAID card and AMM, and network card and all kinds of other internal hardware. It can take a day for a fully occupied BladeCenter. Then it lets you chain-boot into a Server 2012R2 install CD that you've got to slipstream the latest patches into.
Then AND ONLY THEN does it allow you to boot up into plain Windows without BSOD on bootup, so you can get on with actually installing the proper Windows drivers instead of the Microsoft-supplied ones, configuring the damn thing in terms of network, storage,etc.
Sounds like a horror story? It is. But it's got nothing to do with the Windows CD that Microsoft supply, in the same way that latest-laptop-model-with-Windows-support-only-not-yet-supported-on-Linux has nothing to do with some inherent flaw in Linux.
Typical experience with Linux is more generally "Okay. That seems to have worked. What do I do now?" (which is pretty much Linux use in a nutshell) while sitting at an unaccelerated login screen. I know, I've deployed Linux in schools, and we do it as part of some courses, and I've shown lots of people how to use it.
P.S. If I grab the latest laptop off the production line and slap plain Windows on it, likely I will have similar problems. How do I know? I do it all day long. Best ones are when the wireless or network just won't work, so it can't get to Windows Update to get the rest of the drivers for the machine. And sometimes even the Windows Update drivers just crash the thing or don't work at all. The newer the laptop, the bigger the problem you get.
Would you like me to describe the problem with a brand-new B5400 Lenovo laptop I had that consisted of ONLY joining open wireless networks and not encrypted ones, where only the left half of the touchpad worked properly, the network card didn't work, and the graphics were stuck in 1998 in terms of screen resolutions? Windows is JUST as bad in similar circumstances.