[spystath]

For every couple "just works" cases there is a corresponding "doesn't work at all". Given the diversity of the PC as a hardware platform there are going to be edge cases. There is no avoiding that. I'm fairly certain there are cases where hardware "just works" on Linux but doesn't do so on Windows either because there is no driver any more, or because the driver is borked, or any other reason. And here's my anecdote: the wifi on a windows laptop I had once kept dying or dropping packets randomly. Turned out the shitty Killer wifi driver was doing some kind of "optimisation" <insert hand-waving here> to improve throughput. It took a lot of google-fu to find out what the problem was. And this is where I believe you are wrong wrt the command line. The command line is a powerful diagnostic tool and having text files as configuration is much more accessible than delving into a 13-level deep registry chain.

Now, I'm not claiming that everything is smooth sailing on Linux, because it isn't, but the "I've spend hours trying to debug something" argument can be said for both sides and if it comes to that the mythical "average user" won't be able to sort it out by themselves in either case, command line or not.