zlacker

>>tonyst+(OP)
Yeah, no. Maybe with old laptops, but newer laptops still have their fair share of issues. When I bought my thinkpad A485 kernels wouldn't boot without additional parameters, the graphics would freeze at times and cause a hardlock, sleep and hibernation have been fixed and broken again intermittently over several kernel versions, the wifi card's AP mode started causing segfaults in kernel 5.2 due to the driver's rewrite but has since been fixed, the fnlock key LED didn't update properly, which I spent a while debugging and submitted a kernel patch for, and while over the years the fingerprint scanner has been implemented, it's a pain to install and support for fingerprint scanning in linux is still in a very sorry state. Oh and bluetooth still can't connect more than one device at a time, so I had to buy a dongle to connect two joycon controllers.

Granted, I've always had these kinds of issues with new laptops, especially when it came to proprietary nvidia or AMD graphics (before AMDGPU) and I agree it's improved a lot, but I still need to tell people that there's caveats with some (especially newer) laptops.

>>mid-ki+H5
Ubuntu: Except for Bluetooth and audio, and sometimes it forgets there's a wired Ethernet port I have to down/up the interface with `ip`.

BT is a trainwreck.

>>sbf501+18
Can confirm, my god how terrible BT support can be.

So much for things working on older laptops, my 6ish years old Asus as some weird Intel BT chip that has completely broken drivers on Ubuntu. Not as in that they can't be built or installed, but the damn thing keeps fucking disconnecting and reconnecting every few seconds. It literally would've been better if they hadn't bothered.

But also like in general, at least anyone making any new protocol or standard can rest easy knowing that they cannot possibly fuck up worse than IEEE making the bluetooth spec.