4 ms·
> You can use something like vnc but a "whole desktop in a window" is slower Really? I’ve found x-forwarding much slower and annoying unless the host is on a L
by Redoubts 6y ago
> You can use something like vnc but a "whole desktop in a window" is slower
Really? I’ve found x-forwarding much slower and annoying unless the host is on a LAN.
- zbuf 6y agoI think you've probably answered the question there; there are a lot of hosts on my LAN. X works great.
- GekkePrutser 6y agoYeah even on my cloud boxes it works great. They are physically close though. Ideally if X was still maintained they could incorporate some of the old freeNX / X2go logic that makes it more robust against latency. But I think this usecase is becoming more important again. In the early days of X it was great because we were all using terminals on single powerful machines. Then we moved to desktop and transparency was less of a thing. But now we're moving more and more towards cloud computing again which is not all that different from the old client/server model. At least not in the sense of having a separation between compute and I/O.
- galangalalgol 6y agoAgreed, my workflow is a workspace with firefox with jira gitlab etc. open. Then a few with terminals and vscode open, several of those are often vscode running on remote machines via x forwarding. Then I develop on one box that is a couple vpn hops away and its too slow for forwarding. I hate it though because I have to switch to that workspace, fullscreen the window, and then when I'm done, esc the vnc and switch to another workspace. If there is a wayland way to have just firefox or just vscode running remotely that would solve my concern.