First and foremost, sound. I tried to get mixing -- simultaneous playback from different programs -- to work, spent like half an hour on trying to figure out and gave up. On Windows, it works out of the box, so half an hour was more than generous allotment of time.
Next, sleep / resume. Has never worked for me on Linux; at the work place where I used Linux, I just let the machine run overnight. That would be a no-go at home, as I sleep in the same room.
When I got a new machine, I installed Linux only to check that the HW was working and to download Win installation. The kernel had only experimental support for the chipset and integrated graphics (Intel, Skylake just about came out). I had to enable it with boot switches, after which I was able to start GUI (X). However, the GUI randomly and completely froze the machine, a hard reset was required.
I also think that audio mixing didn't work out of the box.
I also tried copy/paste for the fun of it, it did work this time, but only if I managed to guess the "correct" clipboard.
Thanks, but no thanks. $100-ish license that I paid for Windows Professional has paid itself out immensely with things that "just work" out of the box. My time is worth way more than $100.
Thank you for the response. this helped me understand better how people come to conclusions like this.
You want to be able to buy bleeding edge hardware without checking for driver support and have it just work. That is important enough for you to prefer windows for this reason. Fair enough.
Something to think about:
What do you think causes this situation that on day one windows has a stable driver and Linux doesn't? Could it have anything to do with the cooperation of the hardware vendor?
Assuming you actually wanted to run linux, would there be any way you as an end user could work around this problem? Is there anything people could do to improve the overall situation? Maybe something more helpful than puplicly complaining about experimental drivers being experimental?
It's ok if you don't care about this. But characterizing the story above as "linux has driver problems" strikes me as something between superficial and disengenious.
But yeah, you can't always blindly throw the newest Linux at the newest hardware and expect it to work. Free Software requires a a certain amount of taking responsibility for your own computing.
Conclusions like what? That the then-latest linux did not support the then-latest HW is not a conclusion, but a _fact_.
> But characterizing the story above as "linux has driver problems" strikes me as something between superficial and disengenious.
It's disingenious to push back the problem onto the end-user. The "linux community" wants people to use Linux, so it's THEIR responsibility to make it work for the end-user. I don't care about the underlying reasons WHY it doesn't work, it doesn't work.
> But yeah, you can't always blindly throw the newest Linux at the newest hardware and expect it to work.
Well, the CPU + motherboard combo was straight recommended by Intel, and, at that time, I don't think there were any chipsets "supported" by Linux AND the CPU anyway. Should I have bought older-gen HW just to run Linux? Forget it.
> Free Software requires a a certain amount of taking responsibility for your own computing.
Indeed. Free Software is free only if your time is worth nothing. Thanks but no thanks.
If only you could see how entitled and childish you sound.
But I agree: with that mentality, please stay away from any free (as in freedom) software. Please continue paying MS to deal with you and your attitude.
Nobody cares if YOU use linux, certainly not the community.
Another example. Laptop SP513-52N-59M4, Ubuntu 20.04 LTS. Non-operational driver for USB fingerprint sensor ID 04f3:0c03 (ELAN). "Device disconnected" error when trying to add a fingerprint.
Probably not a driver problem, but screen tearing while playing youtube videos is annoying.
