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
With Wayland, Gnome and KDE have no way to adjust the scroll speed on a laptop trackpad. Not the pointer speed, the scroll speed.

In 2022.

That is the kind of basic thing that does not work.

In addition to that, if you have a high-DPI laptop display and you want to plug it into a low-DPI desktop monitor (or vice-versa), good luck getting the scaling to work in a usable way.

>>_skel+Eu
> In addition to that, if you have a high-DPI laptop display and you want to plug it into a low-DPI desktop monitor (or vice-versa), good luck getting the scaling to work in a usable way.

Sure? This is exactly the thing that Wayland was supposed to solve. Only X has one DPI for all screens.

I still use X because I'm on FreeBSD and I even got multi-screen multi-dpi scaling to work there, with xrandr settings but indeed it was not fun. In Wayland it should be click & play though.

>>_abox+tK
Wayland supports it quite well but any app that uses the legacy XWayland compatibility layer does not work. Which is basically everything using Electron.

It's not a fault of Wayland but it is reflective of the whole Linux laptop experience.

>>Gigach+fN
If it's using a recent build of Electron you can in fact use proper Wayland. Electron supports it, if something doesn't; they're on an old version.

Even sharing with the help of various 'portals', e.g. xdg-desktop-portal-gnome or xdg-desktop-portal-wlr

It 'simply' takes some arguments at runtime. Below are what I use -- taken from my Sway 'start on login' script [some is superfluous]:

    ElectronThingHere --silent --enable-gpu --use-gl=egl --enable-features='VaapiVideoDecoder,VaapiVideoEncoder,WebRTCPipeWireCapturer,UseOzonePlatform' --ozone-platform=wayland

You'll find they're basically identical to what you'd use to enable/force Wayland on Chrome. Also VAAPI {en,de}coding and pipewire based sharing

You can also replace --ozone-platform=wayland with --ozone-platform-hint=auto for less strong-handed encouragement

I use quite a few different Electron-driven things on Wayland. Discord is the only one seemingly refusing to update their Electron base... and getting free Wayland support

If not for them I'd remove XWayland support entirely from my Sway configuration