[188201]

I wonder how do you solve the technical problem if there was driver issue in Windows.

When I am facing issue in Windows, I google it, then I got some regedit trick to perform. If that works, that's great. If not, then I need to search for another trick until it works. Since windows command line sucks, I have to hop through different configuration windows to try solving the issue. A very frustrating experience.

Could an average Windows user could able to diagnostic their problem and confidently perform an action knowing it will work? My experience is they just ask their friend, family or ask for immediate solution on social media. If they can't solve it, then maybe just buy a new one.

I think Windows is just as accessible as how many friends and family using Windows.

[hiram112]

> I wonder how do you solve the technical problem if there was driver issue in Windows.

This just doesn't happen that often in Windows, at least for the majority of hardware.

Yeah yeah, I know everyone has an anecdote of some graphics card driver update screwing up their multi-monitor setup, or that cheap no-name Chinese headset or camera bought off Amazon that never worked (and which they promptly returned).

But chances are, if you buy a well known branded component at Best Buy or Staples or even online, and you're not running some ancient version of Windows, the drivers will work. At worst, you might have to ask the IT guy at work or your kid who's more tech savvy, and they'll figure it out by downloading the drivers off the OEM's site. They certainly won't need to jump into a command line and compile a patched driver into a kernel like you'll end up having to do on Linux.

The reason for this is because the software engineers who wrote the drivers spent 90% of their time ensuring it would work in "most" versions and configurations of Windows, 9% of their time getting it to work with Mac (maybe), and anywhere from 0% to 1% for Linux.

When I was younger, I really enjoyed the challenge of digging into Linux and learning about how drivers and various subsystems worked. But now... I don't want to spend half my weekend to get a $40 USB camera or headset to work properly. I get paid decent money to write and fix software at work, 50 hours a week, and the novelty of doing it on Linux has long worn off.

[kempbellt]

Purchased a "Microsoft Xbox Wireless Controller + Wireless Adapter for Windows 10" off Amazon.

Brand is Microsoft and it is designed for Windows 10. (Non-affiliate link: https://www.amazon.com/gp/product/B078T3R8YS)

Plugged it into a USB 3.0 port on my Windows 10 machine. Hardware not recognized. Clicked, "Search automatically for drivers" (which has maybe worked once, ever), No drivers found.

Went to Google... All the "support" answers that you see from microsoft when you google "drivers for windows 10 xbox controller" provide basic IT support responses and no links to drivers. Found a link on reddit somewhere to a microsoft page where I finally found drivers that worked.

> if you buy a well known branded component at Best Buy or Staples or even online, and you're not running some ancient version of Windows, the drivers will work

Microsoft brand main stream product (over 5000 reviews on amazon), doesn't work out of the box on Windows 10...

I can't say that my personal experience is in line with anything you mention, re "things working out of the box on windows more than mac or linux".

[188201]

Just buy a piece of hardware that is compatible with Linux and then you get a pain free experience.

I am more productive when enjoying higher IO throughput on linux file system. Windows's program was always unresponsive and hurting my productivity.

Another example is an unknown driver bug could cause Windows system process go up to 100% CPU usage and there are no obvious solution to the problem. I don't think average user like it. They just think computer is generally buggy and accept that. They don't know anything better.

[disqard]

The last paragraph in your response really resonates with me. My time is much more valuable now, than it was when I'd find excuses to tinker with my tools.

Today, I just want my tools to work, and I want to use those tools to get things done.