Linked by Thom Holwerda on Tue 2nd Jun 2009 17:15 UTC, submitted by lemur2
X11, Window Managers FSM has an article about improvements coming our way in X.org. "There's more coming our way than 'mere' graphical goodness: Xorg developers are about to unleash upon us more performance and ease of use than X ever knew before. Not only that, the work being done now will allow older hardware to perform better and new hardware to be supported faster."
Thread beginning with comment 366852
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: a fun read.
by JAlexoid on Wed 3rd Jun 2009 20:07 UTC in reply to "RE[2]: a fun read."
JAlexoid
Member since:
2009-05-19

"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.

Reply Parent Score: 1

RE[4]: a fun read.
by ba1l on Fri 5th Jun 2009 14:40 in reply to "RE[3]: a fun read."
ba1l Member since:
2007-09-08

You're making the assumption that X uses networking on local clients, which is wrong. Connecting to a local X server uses a local unix domain socket, and much of the bulk data transfer between the client and the server is done using shared memory. Those are pretty much the fastest IPC mechanisms available on a Unix system.

The X protocol is a little chatty, and often requires rather more round trips than you might otherwise need. This is improved with newer X extensions and libraries (XCB, for example, handles this better than Xlib).

None of this is a fundamental design problem.

By the way, Windows works the same way. The display server process (which resides in the kernel in Windows XP, and as a separate process in Vista) communicates with applications using local IPC mechanisms and shared memory. Any impression the API gives that you have direct hardware access is an illusion, and always has been on Windows NT systems. It may have been true on 16-bit Windows and Windows 9x, but it has never been true on Windows NT based systems.

Reply Parent Score: 1