* It broke screen sharing things
* It removed X forwarding
* It made my copy-paste life more complicated
* It made steam ui ever slower
Were these points fixed? what is the current usability of Wayland on these fronts?
Sometimes it's their annoying chrome-fork, steam-web-runner or whatever in a constant crash-loop in the background, eating all CPU.
Other times it seems like if a game or the UI gets launched accidentally or automatically somehow on the integrated graphics, I have to go hunting zombie processes with kill -9 to get things to shut down enough so that I can start them using discrete graphics.
Sometimes launches games and they're in odd geometry.
Running it on X instead of Wayland sometimes fixes problems. But then other times not. Unpredictable.
They're using a chromium based shell, but I don't have these problems with other things like that (Slack, Chrome itself, etc.) And Wayland support in the chromium stack is ... ok? So what gives?
But the Steam client is weirdly dodgy, even though it should just be a web UI that makes a few system calls. It's much worse than an Electron app like Visual Studio Code.
There's the next-gen Steam Deck UI which is less buggy but pushes a lot of graphics cards pretty hard.