The Wayland way is probably to grab the framebuffer and encode it to a video and stream that over the network, like the game streaming services do already. Isn't it way inefficient? Yes, but with specialized hardware (GPUs) it may be doable on even mobile hardware. Windows RDP to Linux xfreedrp (Remmina) is probably the best experience for me right now. x11vnc is just crazy simple to get going when I need desktop access over SSH, but it is also not being maintained.
My point is that it's not a priority (at all) and the only thing is frame blasting which requires fat low latency pipes. FreeNX had different goals and had a different transport. Xvnc would actually be the Xrdp side by side equivalent, and it's maintained. But both are doing pretty much the same thing (VNC style underneath). Of course, we could argue that at the time, FreeNX's competition might not have been VNC so much as just plain old X Client, which was/is dog awful slow. Anyhow, posted this so I could attach in response to recent video here: th-cam.com/video/Ly22ZKPGxXs/w-d-xo.html and some where asking for a "better" demo.
The advantage of X2Go is that it's extremely fast, but I don't think it works in Wayland, and besides, I think Wayland is dead on arrival. I was real exited about it when it was announced, back in 2008, 15 years ago. Seemed silly to be using the loopback interface to communicate locally, well, X11 doesn't do that anymore, it bypasses it and uses a direct frame buffer, but it's maintained because some programs do direct access to the loopback interface. VNC doesn't even COMPARE to X2Go although I would not recommend using either GNome or KDE with it - they just don't tend to play well, use LXDE or some other simpler desktop. You won't have 3d desktop effects anyhow though X2Go. X2Go is on part with MSTSC (i.e. RDP) in terms of speed. When working on a LAN, you can't even tell you're on a remote machine unless you fire of a video player in full screen.
Piece of advice, DON'T - KDE will rearrange your desktop icons if you start up with a lower resolution with X2Go, it will happily PERMANENTLY rearrange your widgets to fit on the screen, sometimes even overlapping them and there's no way to prevent it so when you next startup KDE on the machine you remoted too, it's all screwed up. Stick with LXDE and XFCE - they aren't beautiful, but they're usable. You won't have any desktop effects with KDE either. I don't recommend trying with GNOME 3.0 either. Stick with a simple window manager. Remote desktop is for work anyhow and you can always throw up your X2GO session in one virtual desktop, and still have access to others on your local machine. Another thing you CAN do is on X2Go instead of selecting a desktop select "Single Application", and just startup a konsole, you might need to specify the full path on the local machine. From there you can launch anything from the command line. You might have varying luck with this. Once you close the konsole, all applications should also disconnect, and MAYBE you will be able to resume them on next connection. I've have varying degrees of luck with it.
You call this heavy stuttering , really good job ? 🤣🤣🤣. Did you ever used sunshine and moonlight ? That is good performance its 4k@120fps with 30ms latency. Please dont call this good. Its horrible
You talk real stuff.
The Wayland way is probably to grab the framebuffer and encode it to a video and stream that over the network, like the game streaming services do already. Isn't it way inefficient? Yes, but with specialized hardware (GPUs) it may be doable on even mobile hardware.
Windows RDP to Linux xfreedrp (Remmina) is probably the best experience for me right now. x11vnc is just crazy simple to get going when I need desktop access over SSH, but it is also not being maintained.
My point is that it's not a priority (at all) and the only thing is frame blasting which requires fat low latency pipes. FreeNX had different goals and had a different transport. Xvnc would actually be the Xrdp side by side equivalent, and it's maintained. But both are doing pretty much the same thing (VNC style underneath). Of course, we could argue that at the time, FreeNX's competition might not have been VNC so much as just plain old X Client, which was/is dog awful slow. Anyhow, posted this so I could attach in response to recent video here: th-cam.com/video/Ly22ZKPGxXs/w-d-xo.html and some where asking for a "better" demo.
The advantage of X2Go is that it's extremely fast, but I don't think it works in Wayland, and besides, I think Wayland is dead on arrival. I was real exited about it when it was announced, back in 2008, 15 years ago. Seemed silly to be using the loopback interface to communicate locally, well, X11 doesn't do that anymore, it bypasses it and uses a direct frame buffer, but it's maintained because some programs do direct access to the loopback interface.
VNC doesn't even COMPARE to X2Go although I would not recommend using either GNome or KDE with it - they just don't tend to play well, use LXDE or some other simpler desktop. You won't have 3d desktop effects anyhow though X2Go. X2Go is on part with MSTSC (i.e. RDP) in terms of speed. When working on a LAN, you can't even tell you're on a remote machine unless you fire of a video player in full screen.
How did you get a KDE 5 Desktop over x2go? For me that fails and I have to switch to xfce on the remote machine.
Custom Desktop -> /usr/bin/startplasma-x11
Piece of advice, DON'T - KDE will rearrange your desktop icons if you start up with a lower resolution with X2Go, it will happily PERMANENTLY rearrange your widgets to fit on the screen, sometimes even overlapping them and there's no way to prevent it so when you next startup KDE on the machine you remoted too, it's all screwed up.
Stick with LXDE and XFCE - they aren't beautiful, but they're usable. You won't have any desktop effects with KDE either. I don't recommend trying with GNOME 3.0 either. Stick with a simple window manager. Remote desktop is for work anyhow and you can always throw up your X2GO session in one virtual desktop, and still have access to others on your local machine.
Another thing you CAN do is on X2Go instead of selecting a desktop select "Single Application", and just startup a konsole, you might need to specify the full path on the local machine. From there you can launch anything from the command line. You might have varying luck with this. Once you close the konsole, all applications should also disconnect, and MAYBE you will be able to resume them on next connection. I've have varying degrees of luck with it.
You call this heavy stuttering , really good job ? 🤣🤣🤣. Did you ever used sunshine and moonlight ? That is good performance its 4k@120fps with 30ms latency. Please dont call this good. Its horrible
Bro you tslk too much useless overhead . Compress your information be mire efficient