4 ms·

You mean _parity_ features? SSHing into a server and launching a small GUI tool is still dead. It was killed by Wayland intentionally and willfully as a funda

You mean _parity_ features? SSHing into a server and launching a small GUI tool is still dead. It was killed by Wayland intentionally and willfully as a fundamental design idea. In fact, the feature of doing that is considered "not part of wayland" by Wayland designers. The root problem is that wayland replaced half of x.org and left the rest for someone else to figure out.

jhasse 7y ago
> SSHing into a server and launching a small GUI tool is still dead. They are working on native support for that via PipeWire. For the time being you can still do that with Xwayland.
- erik_seaberg 7y ago
  PipeWire is video streaming, not remote rendering. They're assuming a rack of GPUs in the datacenter and a virtual circuit dedicated to me, but in reality I have a congested link and one GPU attached to my display.
  - vardump 7y ago
    The question is, which is more data. Rendered result or the data to do the rendering. If the rendered result is lighter, then a video stream makes perfect sense. If sending the data over to render is lighter, there's still one more issue: that GPUs are still not interchangeable, and the server hosting the application needs to have the necessary information about all the possible GPUs, their quirks and limitations. And you might still get inconsistent results at various clients. My personal guess is that the data to render is a lot more than data the required to do video streaming. So much depends on doing CPU rendering directly to textures. Although more and more is moving to GPU, so...
  - Dylan16807 7y ago
    X forwarding is pretty awful over congested links and high-latency links in my experience. And from what I've seen if a program has even a medium-low level of graphical intensity it's not going to interact well with X forwarding. So anything that previously worked, should still work without a GPU.
zeroXinfinity 7y ago
There have been a few attempts to patch the core library, most notably [0], but those have fizzled out, probably because they'd break backwards compatibility. (Another victim of "We'll figure it out later".) The most recent work appears to be a work in progress tool for this at [1], but it's also the sort of thing that could have, and should have, been done 10 years ago. [0] https://web.archive.org/web/20170302095534/http://blogs.s-osg.org/wow-wayland-over-wire/ https://web.archive.org/web/20170302095534/http://blogs.s-os... [1] https://gitlab.freedesktop.org/mstoeckl/waypipe/ https://gitlab.freedesktop.org/mstoeckl/waypipe/
okennedy 7y ago
Synergy (https://symless.com/synergy https://symless.com/synergy) is something that I've been searching for a good, Wayland-compatible, replacement for. It's simple, but I've gotten very accustomed to the ability to plop down a laptop (Mac, Linux, whatever) next to my desktop and instantly have another screen-worth of real estate to work with. Wayland, by all accounts I've seen to date, just doesn't have the hooks to allow a tool like Synergy to exist. :(

jhasse 7y ago

> SSHing into a server and launching a small GUI tool is still dead. They are working on native support for that via PipeWire. For the time being you can still do that with Xwayland.

erik_seaberg 7y ago
PipeWire is video streaming, not remote rendering. They're assuming a rack of GPUs in the datacenter and a virtual circuit dedicated to me, but in reality I have a congested link and one GPU attached to my display.
- vardump 7y ago
  The question is, which is more data. Rendered result or the data to do the rendering. If the rendered result is lighter, then a video stream makes perfect sense. If sending the data over to render is lighter, there's still one more issue: that GPUs are still not interchangeable, and the server hosting the application needs to have the necessary information about all the possible GPUs, their quirks and limitations. And you might still get inconsistent results at various clients. My personal guess is that the data to render is a lot more than data the required to do video streaming. So much depends on doing CPU rendering directly to textures. Although more and more is moving to GPU, so...
- Dylan16807 7y ago
  X forwarding is pretty awful over congested links and high-latency links in my experience. And from what I've seen if a program has even a medium-low level of graphical intensity it's not going to interact well with X forwarding. So anything that previously worked, should still work without a GPU.

zeroXinfinity 7y ago

There have been a few attempts to patch the core library, most notably [0], but those have fizzled out, probably because they'd break backwards compatibility. (Another victim of "We'll figure it out later".) The most recent work appears to be a work in progress tool for this at [1], but it's also the sort of thing that could have, and should have, been done 10 years ago. [0] https://web.archive.org/web/20170302095534/http://blogs.s-osg.org/wow-wayland-over-wire/ https://web.archive.org/web/20170302095534/http://blogs.s-os... [1] https://gitlab.freedesktop.org/mstoeckl/waypipe/ https://gitlab.freedesktop.org/mstoeckl/waypipe/

okennedy 7y ago

Synergy (https://symless.com/synergy https://symless.com/synergy) is something that I've been searching for a good, Wayland-compatible, replacement for. It's simple, but I've gotten very accustomed to the ability to plop down a laptop (Mac, Linux, whatever) next to my desktop and instantly have another screen-worth of real estate to work with. Wayland, by all accounts I've seen to date, just doesn't have the hooks to allow a tool like Synergy to exist. :(