Hacker News Reader

Yes this. If you use gnome or kde you probably will have no issue with the transition to Wayland. If you use any other window manager then the transition will be painful because there's a bunch of things that don't simply map over from x WMs to Wayland compositors.

I just did this switch and found it incredibly frustrating. Simple things like, "I would like to be able to log out and return to my greeter" don't just work like they do in x.org, and it is dependent on which compositor you use.

> If you use gnome or kde you probably will have no issue with the transition to Wayland

Anecdata but I've had a LOT of issues with kde & wayland, mainly due to SDDM.

> You haven't even mentioned which wayland compositor you are using.

No idea. I'm using Pop OS. So whatever that uses. Gnome is the DE, I think?

>No idea. I'm using Pop OS.

So you're being upvoted to the top by praising how flawless Wayland works on an OS that runs by default on X11? :))

Aww man, I hope there's a miscommunication somewhere, like you switched PopOS from X11 to Wayland, because otherwise this is HN comedy gold.

> like you switched PopOS from X11 to Wayland

> When I tried that with X I got lots of juddery tearing.

They said it pretty explicitly

No, they didn't explicitly say they tried X11 "on the same OS". You can assume that, but it's not explicitly stated in the context. It might as well be experiences on different OSs/instances. OP needs to clarify.

And from my experience, there's distros that work better with X11 which is why they ship with it out of the box instead of Wayland(like Mint, EndeavourOS and Kubuntu), and ones that work better on Wayland out of the box, like Ubuntu and Fedora.

I had to do some pretty hardcore hacking to get Wayland working on Pop.

I wrote it up at https://shkspr.mobi/blog/2020/05/fix-screen-tearing-on-rotat...

Warning - you'll need to be at least a Level 17 Linux expert to understand the complexity involved.

Sorry. Thanks for the laugh :)

And in addition there are vast parts of the API that is deprecated and no longer used, with basically no documentation of what should not be used.

> because time spent on dealing with Gnome or KDE bs is time not spent on more useful things.

The entire reason there's time spent on dealing with Gnome vs KDE vs other bs is that everyone wants to build and customize their own desktop. But hey, it's OSS, freedom of choice and you're free to do it but I doubt window decorations will add very much to the overhead of all those different desktops.

It's the same issue with the "W3C is just a standard." Rather than making the lives of web developers and users easier by just basing every web browser on Chromium we have to deal with caniuse, polyfills, nonstandard extensions. Basic features like tab sharing are implemented by Google's NIH cast protocol. There's no such thing as a website anymore there's Chrome apps, Firefox apps, and Safari apps. More time is spent wrangling webpack then doing actual web development.