News for hackers. Stuff that matters.
Re:Why Your Desktop Won't Be Running Mir/Wayland Anytime Soon by zanny on Saturday March 09, 2013 @12:35AM (#5347509)
> has the Wayland project changed their tune on networkable graphics

You mean "provide a flag in ssh to forward a rendered window?"

They were talking about having hooks so a VNC server could act as a compositor for windows that it can forward over the VNC protocol. That would be a much better solution than raw pixel buffers like X forwarding had.

Re:Why Your Desktop Won't Be Running Mir/Wayland Anytime Soon by npsimons on Monday March 11, 2013 @11:43AM (#5357405)
That is not feature parity, I don't care how much people claim it is. Feature parity is when I can start a GUI program on a remote machine and have its windows show up as if they were running locally. Not some sandbox-separated-desktop-in-it's-own-window, where my keyboard shortcuts and mental map are broken (I can't alt-tab through all my windows now). It drives me nuts how these people claim to be "advancing the user experience" when they obviously don't even care about such basic concepts as consistency (eg, the aforementioned capability of being able to tab through all windows, whether local or remote).
Re:Why Your Desktop Won't Be Running Mir/Wayland Anytime Soon by vsync on Saturday March 09, 2013 @12:51AM (#5347545)
X forwarding is just a tunnel for the normal X protocol, which is both higher-level and provides much more functionality than a raw pixel buffer.
Re:Why Your Desktop Won't Be Running Mir/Wayland Anytime Soon by zanny on Saturday March 09, 2013 @04:40AM (#5347950)
What extra functionality is available in networked X that is not available over a VNC pipe?