There are various solutions already available for remoting in Wayland.
GNOME: https://wiki.gnome.org/Projects/Mutter/RemoteDesktop
KDE: https://userbase.kde.org/Krfb
Sway/wlroots: https://github.com/any1/wayvnc
Generic: https://gitlab.freedesktop.org/mstoeckl/waypipe/
Web-Based: https://github.com/udevbe/greenfield
You can also still use your X11 programs remotely within Wayland, by using XWayland, which is supported by all the major implementations.
Unrelated to Wayland, there is also backend support in GTK3/4 for rendering to a web socket: https://developer.gnome.org/gtk3/stable/gtk-broadway.html
Re:The X-Windows Disaster (1994)
by ricktdotorg on Thursday March 05, 2020 @12:26PM
(#22495719)
from this page:
> GNOME: https://wiki.gnome.org/Projects/Mutter/RemoteDesktop
"Currently only remote passwordless unencrypted VNC access to an existing session is supported."
i guess that is technically a solution, but not a good one.
Yes, the quality of these varies, pick the one that is right for you. X11 forwarding is not without issues either. With VNC you'll probably also want to tunnel the connection over SSH to secure it rather than rely on server authentication anyway.
Re:The X-Windows Disaster (1994)
by s_gourichon on Thursday March 05, 2020 @12:40PM
(#22495902)
This not universally good, but I would never open a port to a VNC server anyway, encrypted or not. Tunneling a passwordless unencrypted protocol through a SSH tunnel is fine, still.
You can use NVIDIA cards with Wayland, you just can't use NVIDIA's proprietary driver with wlroots (which is by no means the only Wayland compositor). Wayland is the default in many distributions, and if you're using one of the more common desktop environments, you'll get by just fine when using the proprietary driver.
Replacing X feels like the nuclear fusion project of the Linux world, constantly receeding into the future even as it maintains its promises of fixing all our problem When It's Done(tm).