WinterSnowfall: You don't have to convince me of the technical superiority of Linux - I'm with you on this one. That was not what I was even attempting to debate.
Neither was I. I was specifically arguing the point that for Linux you'd need to be a "nerd" or that administering a Linux system is harder and more involved than administering Windows.
In quite many cases, I've found the opposite to be true. Quite often even at my work, I have to ask my colleague (who is more about Windows server administration than me) "Ok, so where the heck do I find this option in Windows, or is there such an option at all?". And then I usually get some quite complicated instructions on where to go in the Windows user interface to find that option, in fact usually we need to open a Skype share screen session so he can instruct me specifically where to go and what to choose because even he doesn't necessarily remember it by heart, and it may partly depend on the Windows version as well (as the user interface has changed).
With Linux, the same instructions could be e.g. "copy&paste this line into /etc/fstab and save it, and then give the command "sudo mount a", and you are done.".
Some recent example of that that I remember was when he was instructing me what kind of Windows user we must add, with what kind of privileges and user group memberships, to a Windows server so that we could monitor that system. The instructions were quite convoluted and meant visiting two or three different places, all the relevant options were not in one place. I think we spent at least 30 minutes inspecting and configuring it together, over Skype.
Adding a similar user in Linux is about copy&pasting a couple of commands in the terminal. Takes less than a minute to instruct someone on that over phone.
EDIT: Since I like anecdotal evidence, here is another one:
The machine (be it your workstation or a server) is running out of hard drive space, and you want to see what is eating so much space.
In Windows: With basic Windows tools, it is just too time consuming, you'd have to go through each and every folder from the root, right click and select properties for each separately, then do the same for each subfolder...
So the better way in Windows is that you try to google how to check something like that, and then hopefully you see suggestions to using a third-party utility SpaceSniffer, installing it into your system and running it as an administrator. It gives you a graphical presentation what are the big files on your system, but depeding how big (how many subfolders, files etc. your system has), it can became quite hard to look at that picture it is constructing, and you have to wait quite a long time for it to complete.
In Linux:
cd /
sudo ls -lh
sudo du -hs *
cd <the directory that seemed to contain quite a lot data>
sudo ls -lh
sudo du -hs *
Repeat as many times as necessary, until you find the culprit(s). This is how I recently found how some log file had grown to 64 GB in size on some Linux docker system, and was the reason it had went into an inert state due to low amount of free space. (I am sure it would be trivial to even write a small bash script to go through each and every file in your filesystem, and list them in size order; but above is what I'd suggest for someone to try over phone.).
EDIT2: Well, since this started bugging me, I googled for it and maybe this one command is all that is needed, in order to list all files in your system, in order of their size:
sudo ls -laShR / | more (sorry I didn't get to test that right now, as at this very moment I am indeed on my Windows PC :)).
In Windows in these kind of cases your best hope is that someone, somewhere, has written a separate (graphical) utility specifically for that task. If not, you are screwed.
In Linux it is more probable that some existing command/tool, that is already in your system, can be used for the task.
WinterSnowfall: My point is that some people just don't want to bother with anything that they perceive as even remotely technical, meaning if they can't "click their way out of it", then it's a big no-no. You can't possibly argue Linux is better for those people, because it's simply not meant for them.
In my experience, people overcome such fears by doing it once successfully, and then be like "Well, that wasn't so hard as I feared...".
Lots of this has certainly changed thanks to Google. Now you don't have to know things by heart and experience, or figure it out by yourself. Nowadays you just use the right search keywords in Google, and follow instructions. And my claim is that Linux terminal instructions are often quite much easier to follow, than Windows GUI instructions. The latter usually means a long web page full of pictures of which menu to choose etc., or even a long Youtube video.
Being a "computer wizard" nowadays means that you have basic knowledge of the system, and are good at knowing the right search keywords in google. Very rarely people fight with OS issues that someone else hasn't already fought, even years before.
WinterSnowfall: If you have to consider a scenario, just think what disabling a device would mean for Windows vs Linux. Does clicking on Disable in Device Manager not sound simpler than messing with udev rules or module blacklisting to you? Perhaps you'd say it's not that complicated after all - and I'd agree with you. But you have to understand that for some people this amounts to (at least in perception) taking a few steps vs climbing a mountain.
If the person hasn't used Device Manager before, then I am not convinced they will find the instructions on Windows easier. (Also I am not sure how often a typical user even needs to disable a device... I don't recall if I've ever done that in Windows (or Linux for that matter). Maybe once in Windows, when there was some odd audio pause/lag issue for me in Windows gaming, and googling a long time for it, some suggestions mentioned that there may be too many overlapping audio drivers installed in the Windows system, for reasons unknown; so I followed the instructions how to remove the additional "audio devices").