Now it may happen that no one cares enough about network transparency to bother to write the code, but I don't see that as Wayland's problem.
"I think that a more viable solution in the long run would be to replace the X protocol with a very simple pixel copying protocol that uses the user-level rendering libraries in the application to render to a local image buffer, then copies the pixels over the net in something that looks vaguely like a video stream.
There are a variety of compression hacks that make this surprisingly efficient – this is essentially what the SunRay product does. Some analysis has been done that shows that this uses essentially the same bandwidth as the X protocol, if done well."
From "Window System Design: If I had it to do over again in 2002."
http://labs.oracle.com/features/tenyears/volcd/papers/nrthcu...
http://labs.oracle.com/features/tenyears/volcd/papers/Nrthcu...
Their argument is "A simple pixel encoding protocol requires only modest network resources (as little as a 1Mbps home connection) and is quite competitive with the X protocol."
By that definition everything is network-transparent. Can this do caching of glyphs? Images? All the lessons learned from X and incorporated into NX are ignored. NX is actually usable across high-latency, low-bandwidth links. Streaming bitmaps aren't.
Yes VNC sucks, but MS Windows isn't inherently network transparent, yet remote desktop on Windows provides an absolutely awesome end user experience. It's fast - even over relatively slow connections, it's easy, it even includes sharing of clipboard, sound, drives, and peripherals. And you can easily disconnect/reconnect session.
Everything about the user experience with Windows Remote Desktop is better than any X server implementation I've ever seen.
What would be lost by implementing something similar to Windows Remote Desktop on top of Wayland?
versus
"Nomachine NX is a commercial product starting at $700+ but there's a limited 2 user free version, and also an admin console and a web package. Here's a 14 page PDF with install instructions and a link to the client install guide download location, along with the library version prerequisites..."
Needless to say I use RDP, push install VNC and SSH constantly and have never installed NX or seen a server with it installed or used it. I have my answer.
Why are you wasting time posting on HN about how you're too lazy to evaluate technology solutions properly?
Like most people, all my 'desktop' apps are local - am I not allowed to have a protocol that sacrifices network transparency for local performance?
(like most people, all my remote apps are web apps)
If you're happy giving up X and SSH and doing everything through the web browser, that's ok. Some people like television. I like to get work done. When the "cloud" (some machine in some datacenter in the USA) goes down, don't say Stallman didn't warn you: http://www.guardian.co.uk/technology/2008/sep/29/cloud.compu...
- As a dev/admin, I depend on SSH but not on X.
- The "dangers of cloud" argument is not exactly helping the pitch for network transparency. :)
Being network-transparent does not mean being complicated. See the Plan9 window systems:
Why not try to fix it? This isn't the fault of network transparency or even the X11 protocol, but the tools.
"oops, lost the network connection for a minute? crap, there goes the entire app"
How is that different from losing your SSH connection? There's a screen-like program for X that gives you persistent applications: http://code.google.com/p/partiwm/wiki/xpra
X supporters don't like network transparency, people who like network transparency defend X.
EDIT: After looking at the Wayland mailing list, it seems there are already people hard at work getting network transparency in. So we can probably expect it in the medium run rather than the long run.
http://news.ycombinator.com/item?id=1872536
I flamed a lot. NETWORK TRANSPARENCY IS IMPORTANT. The effort put into Wayland would be much better put into getting NX standardized as the next generation of X protocol, and developing additional X extensions.
David Täht has some good perspective on X11 network transparency:
http://the-edge.blogspot.com/2007/10/x11-is-dead-long-live-x...