X forwarding "just works" in Wayland via XWayland. None of that has changed significantly.
But I'm disappointed to see this myth keep popping up. X in general isn't "network transparent." Some X11 clients are, but only if they're built in a very specific way, which also tends to degrade performance locally.
Thanks for the effort you are putting into comments here lately! Maybe you have ideas on improving the "Are we Wayland yet?" site: https://github.com/mpsq/arewewaylandyet Yesterday I sent a PR for a "Missing" section.
There isn't much for me to say. To be honest, I would probably not contribute to that website. Wayland isn't that exciting of a technology and I don't think end users should even need to care about it or care that any of those utilities supports Wayland, if distro developers are doing their jobs then it will all "just work" and nobody has to worry about it. Also that website is misleading, many of those utilities are wlroots specific and not really useful on other implementations.
It may be an Ubuntu issue then. I’ve tried to start gnome-terminal on the Linux laptop from the Mac running XQuartz and what happened was a terminal starting on my screen on the Linux box, totally ignoring I was sshing into the Linux machine from the Mac.
Maybe you were using the wayland backend, you might have to force X11 with the environment variable "GDK_BACKEND=x11".
Though part of this weirdness is due to the clunkiness of the way X forwarding is implemented, I wish there was a way to do it that didn't involve kludging around with environment variables. But that is what we are stuck with.
I routinely use a program that renders X protocol, gitk, remotely, forwarded via SSH tunnel through a Wireguard VPN.
If there is a better way to do that, I would welcome knowing it. Also, how one would achieve the same result for a Wayland program.
That will continue to work in Wayland, they haven't broken X forwarding. It works similarly to how XQuartz works on the mac.
I can relate as I'm one of the few people I personally know who has used that feature in the last twenty years. In the last ten years or so however, I used some variation of NX in any case, whenever I needed a remote X application, as then I typically need to preserve the session as well. I think the last time I used plain X11 protocol across the network was when I still had Sun Rays (between the Sun Ray server and the application's host).
Wayland is not the only thing thats lead to this. Modern Qt apps work so badly over network transparency as to be totally unusable.
Most toolkits now use client-side text rendering which makes using X strictly worse than VNC for remoting.
Yet another reason to dislike Qt.
Waypipe has entered the chat.
This, IMHO, is the most tragic loss in functionality desktop systems suffered.
It’s hard to justify being unable to do something we’ve done since the mid 90’s. The fact I could sit in front of a computer while running GUI software from different machines with different OSs as if they were local and that, now, the best I can hope for is what VNC gave me in the early 2000’s is nothing short of depressing.