10 ms·
I'm very ignorant about Xwayland – but I frequently use "ssh -Y" or "ssh -X". Is there a simple alternative? Will this move break lots of things needlessly? Th
by azalemeth 5y ago
I'm very ignorant about Xwayland – but I frequently use "ssh -Y" or "ssh -X". Is there a simple alternative?
Will this move break lots of things needlessly? The wayland / X debate is one of those things that I fear will become a bit like vim vs emacs...
- capitainenemo 5y agoI'm still a big fan, personally, of ssh -YC - it works pretty efficiently with Eclipse and other simple GTK text based apps. With Firefox, it doesn't work as well, and I can understand why. Browsers demand a lot of graphics acceleration. That said, you can still get decent performance by force-enabling xrender as long as they still support it.gfx.xrender.enabled;true Personally, gonna be a bit sad when Wayland breaks all my things (my xdotool scripts, my ssh -YC, my XSDL on Android)
- chousuke 5y agoI've run Wayland Firefox over waypipe. It's a bit finicky to set up, but fast enough that you can play videos with no trouble.
- md8z 5y agoXdotool is actually (yet another) one of those things in X11 that is somewhat broken and due for a redesign. The APIs that it uses are not really safe for applications to use, they're meant for window managers, so in some situations your scripts can get overridden by the window manager and they just won't work. For remoting to a smartphone you can just use any old VNC client.
- pessimizer 5y ago> vim vs emacs Is that actually something to fear? They're both available and active, and systems don't depend on either of them being installed.
- amarshall 5y agoWaypipe https://gitlab.freedesktop.org/mstoeckl/waypipe/ https://gitlab.freedesktop.org/mstoeckl/waypipe/
- md8z 5y agoWaypipe isn't relevant in this case, this post is about remotely invoking an RPC call over D-Bus. It's actually pretty trivial to forward a D-Bus socket using ssh -L.
- deleted 5y ago[deleted]
- gspr 5y agoIt's lovely. Some elaboration: Waypipe takes a completely different approach from X forwarding. X forwarding entails shipping a bunch of X drawing commands across the network. This is incredibly inefficient for modern use-cases, where local rendering would be done through direct rendering instead (more details here: https://superuser.com/a/1217295/58251 https://superuser.com/a/1217295/58251). Waypipe takes a step back and instead just renders a low-latency H264 video stream that it ships across the network. It won't be pixel-perfect, but a lot snappier! (In principle there's no obstacle to doing it pixel-perfect either, at the expense of bandwidth)
- AshamedCaptain 5y agoWtf? Sending drawing commands over the wire is WAY more efficient for the vast majority of cases than sending compressed H264 video, and DEFINITELY much lower latency no matter what the codec latency is! It was even mentioned as a con of Wayland in the recent story "What is wrong with desktop Linux" right here on HN.
- dyingkneepad 5y agoThe problem with X11 drawing commands is that there are a lot of round-trips over the network. Client asks for something, has to wait for the server response before proceeding, then it asks something else, etc. XCB tries to help mitigate problems that Xlib created that were not in the X11 protocol, but it's still highly inefficient. In practice, running everything locally and then just streaming the framebuffer ends up being faster. Not that we couldn't come up with a fast-over-the-network protocol. It's just that it's not really here.