[wereallterrrist]

Damn near pure FUD with any remotely, remotely mainstream laptop. The Linux ecosystem is so wildly more consistent and predictable than Win10.

I mean, my laptop doesn't overheat daily in my bag when its booted to Linux, but yeah, Windows is so easy. /s

[ShockedUnicorn]

I'm unsure what you mean with mainstream laptop, but with my Asus zenbook I had these problems:

* Sleeping doesn't work, hibernate sometimes work

* Keyboard buttons for screen brightness doesn't work

* Ambient light sensor doesn't work

* Vsync doesn't work

* Processor always highly clocked, draining battery

I was able to fix some of the issues in Ubuntu by compiling kernel addons of some sort. When I switched to Arch I could with the help of their Wiki fix all of the issues, but there was lot of text config files to edit, and some more compiling of kernel stuff. Even after that I still couldn't get vsync to work properly. Watching youtube while the screen is tearing all the time is very annoying.

If you want to run linux you should get a laptop that is validated to work, like framework or validated dell laptops. At least then you might only need to fix one or two issues.

[wereallterrrist]

Power-profile-daemon, wayland, and running a somewhat recent kernel will likely resolve these except the keyboard shortcuts (though, likely a newer libinput with wayland instead of X will also resolce this).

Which zenbook? Ill try to find one here to validate explicitly.

Its hard to have these conversations sometimes because people use old versions of meh distros and then carry their anecdotes forward for years.

I literally cannot find a Zenbook on the market that has hardware that should have these issues. I'd really, really like to know what custom kernel patches (really?) you were taking to get hardware to work.

[opan]

Have you tried Wayland to fix the tearing?

[froggit]

> I mean, my laptop doesn't overheat daily in my bag when its booted... /s

When you say booting in your bag, are you describing the act of intentionally booting it without removing it from the bag while the bag is open (because taking it out of the bag is a surprising amount of seemingly unnecessary effort) or the "why is my bag warm to the touch oh shit my compy's on" surprise wake from sleep while the bag is closed (because, at least in Windows, there are some events that can wake a compy from S3 sleep at bad times, such as moving it, not moving it, or exposing it to oxygen)?

The latter was quite jarring the first time it happened and so far the only workaround I've found is hibernating the computer before packing it up (which isn't a big deal, but bothers me anyway, because I don't move it often enough to make hibernation my default "lid closed" action).

[wereallterrrist]

I mean there's a serious bug where Windows will not properly realize it needs to /stay asleep/ and will wake itself up in your bag, and sometimes stay on.

Linus did a whole video on it - you have to unplug your laptop, then close it, or risk a serious issue.

Just one example of hoops that Windows users become conditioned to.