Wayland experiences seem to vary wildly. It was most certainly not working fine for me six years ago. Well, six years ago I don't think I got as far as trying screenshots, I'd run into basic window placement or rendering issues that made the system unusable.
But say a couple years ago, I definitely had screenshot issues. Sometimes it just wouldn't capture a screenshot. Or I could only capture one monitor and not the other. Or I had graphical artifacts while drawing the snipping rectangle. Or the screenshot would be taken fine and fail to copy to the clipboard.
I'm well aware people's experiences are very different based on their setup and the implementations used but for me, last year was the first time I could do some work on Wayland without running into major issues, at least until I got to the part where I'd normally use ssh -X.
You have always been able to do ssh -X from a wayland client to a remote X as long as xwayland was running locally.
And waypipe has been solving this need to run a remote app on a wayland remote system. And it performs way better than X forwarding actually. With ssh -X you also need to remember obscure environment variables (looking at you QT) to not have unusable blank windows on some apps.
But say a couple years ago, I definitely had screenshot issues. Sometimes it just wouldn't capture a screenshot. Or I could only capture one monitor and not the other. Or I had graphical artifacts while drawing the snipping rectangle. Or the screenshot would be taken fine and fail to copy to the clipboard.
I'm well aware people's experiences are very different based on their setup and the implementations used but for me, last year was the first time I could do some work on Wayland without running into major issues, at least until I got to the part where I'd normally use ssh -X.