4 ms·
I mean, when your default use-case includes remote rendering of a GUI to clients, you're going to end up with a complex protocol. In the era of heavy servers an
by mbreese 4y ago
I mean, when your default use-case includes remote rendering of a GUI to clients, you're going to end up with a complex protocol. In the era of heavy servers and thin clients, it makes a lot of sense.
But when most (every?) computer includes some kind of GPU, local rendering makes the most sense -- especially when that's how your primary competitors work.
I don't know enough about Wayland vs X11 to make an informed statement, but I do appreciate that Wayland explicitly didn't try to include remote rendering. Let's just leave that up to other protocols (VNC/RDP/etc...). Now if we can just get one of those protocols to work on an individual application/window basis as opposed to the whole desktop.
- simcop2387 4y agoThat would be waypipe, https://gitlab.freedesktop.org/mstoeckl/waypipe#:~:text=waypipe%20is%20a%20proxy%20for,%2DX%20%5B1%5D%20feasible https://gitlab.freedesktop.org/mstoeckl/waypipe#:~:text=wayp....