> It's baffling to me that anyone is still using X Window (no 's', by the way) > in 2010.
People still use Unix command line tools decades after its use. Just because its old doesn't mean that its bad. Do you really think that changing the desktop language abstraction will magically wipe away the single worst feature in most Linux systems: Display drivers. They will always make the difference between performance and not. Most of my problems with X over the years (and there have been many) have related to buggy, broken drivers doing stupid or just plain wrong things. Do you think that hanging the visual screen paradigm will really cause all these problems go away? > The idea of a remote window display was revolutionary when it came out, but > it just didn't live up to the expectations. Firstly, when running locally, X applications run almost directly against graphics hardware anyway, so the 'protocol overhead' or whatever propaganda you've been knocked over the head with over the years just isn't true. Secondly, X applications work over the network, and even though it doesn't work as well over non-LAN conditions, it still works. I've never bothered to use X through the NX protocol, but apparently it makes network based X communications very fast. > What's even more interesting is that Microsoft Windows started from the > other end (a local Windowing system) but when it came to adding remoteness, > not only was it pretty quick but their remote desktop client is actually > orders of magnitude better than an X Window one. RDC is faster and it > supports all kinds of odd cases (mouse wheel, sound, alt-tab, etc...) that X > Window never really figured out. Um, all these things work find with X server except for sound, because X window is a display and input system, not a sound system. Sound can be forwarded as well, if you EVER use it when remoting to other systems. If the wheel is broken, then blame your X server implementation. Alt-tab is completely dependent on your X Server' window manager and the window management managed by your OS. If you know how to configure it, then it works like native apps. RDP on the other hand sends compressed images from the server to the client, and you never have application level windowing from the remote source unless you're paying up the nose for citrix. PS: You can always simulate the RDP experience in X window if you ran something like gnome-session which bootstraps an entire X client session instead of just apps piece meal. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
