[blockmeifyoucan]

> Skylake

From this I gather that we are talking ~5 years ago?

> First and foremost, sound. I tried to get mixing -- simultaneous playback from different programs

I remember this being a problem 10 years ago, but not since pulseaudio.

> sleep / resume

I successfully use systemctl suspend a lot. But yeah, depends on the hardware, def. a pain point.

> experimental support for the chipset [...] completely froze

Not sure what to respond to this. Experimental drivers are expected to be, well, experimental, as in highly unstable.

> clipboard

Ok.

Thanks for the info, this will be helpful to know what to look out for when getting New hardware.

[zvrba]

> Not sure what to respond to this. Experimental drivers are expected to be, well, experimental, as in highly unstable.

This is what to make of this: The then-latest linux kernel did not support then-latest hardware.

[blockmeifyoucan]

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.

[zvrba]

> how people come to conclusions like this

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.

[blockmeifyoucan]

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.

[zvrba]

You know, I feel myself more "free" when using MS products then when I use Linux.