Re: Not my fault you can't use it right.
@ Esme
I work in IT as a systems analyst and do a bit of 1st line/3rd line support as needed.
I can see you are not really recently experienced with the true state of hardware found INSIDE laptops these days.
After reinstalling windows via the method of the manufacturer (not necessarily talking about big guys like Dell etc) you find that half the hardware wont work because the stuff they put inside is non-standard enough for windows (8.1 and 10 are used) to not locate a driver automatically via windows update.
So, you go and try to use the vendors driver disc that has ancient and possibly buggy drivers that caused you to reinstall in the first place as recommended you do so by kind windowsy support peeps you found in the internet. This disc, hopefully you did not throw away. Hopefully the vendor provided you with the disc and you dont need to download it.
Hopefully the disc contains just the drivers you need, and not ones for other laptops that throw up errors when you try to install them causing you to talk to the same nice windowsy peeps who will tell you to either reinstall/refresh windows again or to open up device manager (good luck finding that) and googling the PCI hardware ID of the device to locate a device driver.
A device driver that is not provided from the original manufacturer because they are chinese and only make the chip, not the PCB and rely of the laptop vendor to provide drivers, which they may not do so without proof of purchase (pc specialist, I'm looking at you) which you dont have any more leaving you t wonder why you didnt just buy that ASUS machine, as they have a driver for the same PCI hardware ID but it wont install because you are not using an ASUS.
If hardware dont work in Linux, its so much simpler! Its either not going to work for a while or never will. None of this faffing about trying to get something working again only to discover that it having worked at all the first time round was simply a miracle.
Imagine if your TV remote stopped working due to dead batteries. You go and get batteries for it to find that it uses a non-standard size that nobody stocks but some guy from china on ebay can get you one for more than the cost of a universal remote that stakes standard AA's. So you get the universal remote to find that it wont work with your TV but only with the previous model as the codes changed.
You discover that the codes were added later and can be uploaded to your remote!
So you download the update, run it to be told that there is an error. You google the error to find you need to install .Net 3.5 whoch requires running DISM from the command line and having a valid windows install disc...
I think I've made my point about the state of windows driver support vs linux. It can be a load of shit no matter which OS you are using. Your point is moot.