4 ms·
You haven't even mentioned which wayland compositor you are using. Which is one of the biggest problems with Wayland - there isn't just one Wayland but Gnome W
by account42 3y ago
You haven't even mentioned which wayland compositor you are using.
Which is one of the biggest problems with Wayland - there isn't just one Wayland but Gnome Wayland and KDE Wayland and wlroots-based Wayland and Gamescope Wayland. What functionality is available and working and using which API varies between all of these. This includes really basic things like window decorations.
This is different from X where the core functionality is common because everyone usees X.org. If all the Wayland compositors agreed on how thing should work then multiple implementations would be much less of a problem. But they don't or at lest take ages until all but one of the NIH protocol extensions get abandoned. Some of this protocol extension zoo is hidden by applications and toolkits implementing multiple variants but even if you no longer see it as an end user this is still a cost because time spent on dealing with Gnome or KDE bs is time not spent on more useful things.
- psanford 3y agoYes 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.
- lucideer 3y ago> 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.
- hollerith 3y ago[flagged]
- psanford 3y ago> "Things don't work the way they do in x.org" That is not what I said, please don't misquote me. I said: > [things] don't _just_ work like they do in x.org Maybe it wasn't clear in my post above so let me clarify. A lot of thing "just work" in x.org and don't in wayland compositors. That is the complaint. That things which were easy are now hard.
- marrs 3y ago> so you have to adapt No I don't. X11 works perfectly well for me. Wayland doesn't. Until I can migrate without issue, I'll be sticking with what works. If it gets to a point where Linux becomes unusable for me, I'll just move to an OS that works. Linux isn't the only game in town. Boo hoo.
- edent 3y ago> 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?
- FirmwareBurner 3y ago>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.
- nwsm 3y ago> 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
- FirmwareBurner 3y agoNo, 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.
- edent 3y agoI 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-rotated-external-monitors-ubuntu-pop_os/ 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.
- FirmwareBurner 3y ago
- yxhuvud 3y agoAnd 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.
- Spivak 3y agoIt'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.
- bzzzt 3y ago> 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.