Linked by Thom Holwerda on Sat 28th Jun 2008 22:09 UTC, submitted by diegocg
X11, Window Managers "Maybe I'm just naive, but designing a graphics API such that all image data had to be sent over a socket to another process every time the image needed to be drawn seems like complete idiocy. Unfortunately, that is precisely what the X Window System forces a program to do, and exactly what Cairo does when drawing images in Linux - a full copy of the image data, send to another process, no less, every time it is drawn. One would think there would be some room for improvement. Unsurprisingly, others felt the same way about X, and decided to write an extension, Xlib Shm or XShm for short, that allows images to placed in a shared memory segment from which the X server reads which allows the program to avoid the memory copy. GTK already makes use of the XShm extension, and it seems like a good idea to see if Gecko couldn't do the same."
Thread beginning with comment 320591
To read all comments associated with this story, please click here.
Very nice Discussion
by hackus on Sun 29th Jun 2008 17:20 UTC
Member since:

Reading some of the comments with, xorg now at 1.5 RC2 leads me to point out that really, I feel X was way way WAY ahead of its time both in conceptual implementation and execution.

Working as I have in software engineering and networking now for over 20 years I believe that the direction to smaller portable computing devices like my eeePC for example is going to be the future.

For example, the arguments put forth for local and remote cases for display processing with regards to how X does things, are quickly becomming clear that a remote facility for data both video and audio is going to be required. I mean, I am not going to chug along my 12 pound 8 core laptop with me, when all I need is a NX session to it from my eeePC 900.

Which, is what I do right now.

Performance is grand, anywhere I go.

I can pull up mplayer on my laptop, and start watching my favorite lizard blow the hell out of Tokyo, while using linphone to take a call from work.

All over NX.

I think the dual approach is best. Most of the arguments would seem to be how can we do either one BETTER.

This design though, network centric to be sure, is only now demonstrating its full potential, and it has taken some time for networks to catch up.

I think the discussions are good for the continued improvements that X has undergone.

I mean, lets not forget:

X broke free from the bonds of XFree86 stifiling influences after many people, including me and many others on this list recognized X was moving way too slow to assault the Microsoft desktop.

X is rapidly changing to meet the needs of GNOME and KDE requirements through input from the

Corporations like ATI are recognizing the above advantages of X and are providing open source drivers because their customer bases also recognize these facts and demand the hardware that they buy works 100% feature wise on GPL software.

We are making progress on this stuff you know. In the past year I would say the progress has moved from fast to BLAZING WARP SPEED.

Now, all we need is to get Blizzard to make a native version of Diablo 3 for Linux.

I bet that would help the cause a bit..especially since I am almost sure that neck and neck, Linux will kick Windows arse in display quality and speed if we had the drivers to the hardware opened up.

Now that we do, well....perhaps now is the time?


Reply Score: 3