Linked by Thom Holwerda on Tue 2nd Jun 2009 17:15 UTC, submitted by lemur2
Thread beginning with comment 366691
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Just because Joe Bozo may not use the networking features on his single home Unix computer doesn't mean that enterprise, small businesses, school districts, and such aren't using it.
I can't agree more. I'm primarily an application developer. My own system is a 32bit system. I often ssh to our 64bit development server and run our X11 based IDE their which then displays on my local screen. I then do development work as normal. It's as if my own system is a 64bit server. Awesome!
So yes, I use remote features in X11 often!
"Just because Joe Bozo may not use the networking features on his single home Unix computer doesn't mean that enterprise, small businesses, school districts, and such aren't using it.
I can't agree more. I'm primarily an application developer. My own system is a 32bit system. I often ssh to our 64bit development server and run our X11 based IDE their which then displays on my local screen. I then do development work as normal. It's as if my own system is a 64bit server. Awesome!
So yes, I use remote features in X11 often! "
I agree that that is a useful feature. But still the fact that it's the non replaceable core is dragging performance for people who don't need it.
I really believe that there should be two version of the X:
1. networked one, like the classic
2. as close to the H/W as possible, for the most experience for the single monitor desktop user's like me.
Though I would vote more for having nvidia drivers work with XRandR and having Xinerama style wide worskpace.
One of the main problems is that the x network protocol itself is in its drawing routines very low level, a lot of clients with complex uis can bog down a network significantly. Sure there is help with compressors and protocol mappers but none of those is really standard.
The funny thing is that X is more advanced than other remote protocols in its possibilities but it shows its age in real world useage significantly!
And I agree 99% of all users do not use the remote capabilities but complexity has increased tenfold because of the 1% who need that functionality. I just ask myself often if an approach like rdp to just make hooks were remote functionality can be hooked in is not the better approach!





Member since:
2005-07-11
I do not have a lot X experience, but i always got the feeling X was far too low level and too network oriented. Almost nobody does the remote display as primary method of running programs.
We had ~40 elementary school labs running networked X systems (thin-client setup).
We've since moved over to a diskless client setup (graphics run locally), but we still use networked X to run the occasional software that won't run on the 800 MHz Via CPUs/OpenChrome GPU.
We also provide NX access to our ~15,000 students, to allow them to login to their Linux accounts from home. This uses the network X features behind the scenes.
We also use the network X features to manage our VMWare servers (ssh to server, run vmware, console appears on your local screen).
Just because Joe Bozo may not use the networking features on his single home Unix computer doesn't mean that enterprise, small businesses, school districts, and such aren't using it.