GTK+ 3.8 Released With Support For Wayland
kthreadd writes "Version 3.8 of the GTK+ GUI framework has been released. A new feature in GTK+ 3.8 is support for Wayland 1.0, the display server that will replace X on free desktops. Among the other new features are improved support for theming, fixes to geometry management and improved accessibility. There is also better support for touch, as part of an ongoing effort in making GTK+ touch-aware."
Poor summary. Wayland allows the running of X11 applications through an X server, with work being done to support this on Intel and AMD graphics:
http://lists.freedesktop.org/archives/wayland-devel/2010-November/000292.html
I deny that I have not avoided attaining the opposite of that which I do not want.
What is this "long line" you have been hearing of?
It consists of X, then Wayland.
Just off the top of my head:
Y Window System - http://en.wikipedia.org/wiki/Y_Window_System
Berlin/Fresco - http://en.wikipedia.org/wiki/Fresco_(windowing_system)
Xynth - http://en.wikipedia.org/wiki/Xynth
MicroXwin - http://en.wikipedia.org/wiki/MicroXwin
DirectFB - http://en.wikipedia.org/wiki/Directfb
Mir - http://en.wikipedia.org/wiki/Mir_(display_server)
Then there is whatever Android uses -- SurfaceFlinger?
Well all that does is demonstrate your ignorance of the subject.
There is nothing preventing wayland to be implemented with a remote renderer, and in fact one of the goals of the protocol is to allow efficient remoting (without hampering local drawing).
Seeing as the protocol is being explicitly designed to minimise round-trips, it has potential to be significantly more efficient than remote X.
http://www.h-online.com/open/news/item/Wayland-prototype-for-rendering-software-that-runs-remotely-1715463.html
It's really pretty simple to educate yourself, which is a really good idea if you plan to rant about a subject on a public forum.