Slashdot Mirror
First Steps Towards Network Transparency For Wayland (phoronix.com)
munwin99 writes: For the longest time, when bringing up Wayland a recurring question was 'what about network transparency?!' Well, Samsung's Derek Foreman has today published the set of Wayland patches for providing Wayland network transparency by pushing the Wayland protocol over TCP/IP.
What people want is ssh -X and yes it is a top priority to many.
I concur. VMs, embedded hardware, headless machines- I'm on them all day. And ssh -X is all that I need working for my environment. As long as that works, everything else just is seamless. I think we're not going to see a reduction in VM's. And the number/amount of embedded hardware's only growing.
Now, X certainly has ugly warts. I'm hopeful for what Wayland's offering. This network transparency patch for Wayland sounds like a great start.
--Mark
I do, why am I wrong?
Typical usage : I log onto distant machine, start working in command line (vim, python, matlab -nodesktop), then at some point I will need to display a couple of graphs or images. That's a relatively small graphical payload for which I *do not* want to use VNC. With ssh -X I get the windows to be displayed locally just as if I was doing the work on my light-weight terminal.
This is ludicrous. Wayland is hardly "languishing", and there has been no push on anyone's part to make it the "de factor Linux GUI". It is under development, everyone recognizes it as the next way forward, toolkits and drivers are targeting and supporting it, and it will be adopted when it is ready for adoption.
Anyone using the interim period to scream about network transparency is a moron. Yes, that means you.
I have a different view to yours. I consider Wayland a bit like systemD, a solution in need of a problem, whose final implementation, if the developers can be bothered to go all the way, will be lacking compared to the original.
It's cool to scratch an itch in open source, but live and let live. X has proven itself, people should be improving it, not replacing it, if they want to be relevant to the majority. And they should certainly be very careful about forcing millions of people to change their software stacks if they are working on important foundations of the operating system.
I routinely use X forwarding on a 10 megabit LAN without any problems. More likely a poorly written application is to blame.
The problem is that an X application which is written correctly for local display (for example, taking advantage of hardware acceleration) is "poorly written" for running with a non-local X server, and vice-versa. To handle both cases well you have to implement two different UIs, which shows that X's much-vaunted "network transparency" isn't actually transparent at all.
"The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat