Linked by martini on Tue 23rd Oct 2012 22:02 UTC
X11, Window Managers Wayland 1.0 was officialy released on October 22. Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.
Thread beginning with comment 539938
To read all comments associated with this story, please click here.
So where's the thing...
by Jason Bourne on Wed 24th Oct 2012 22:15 UTC
Jason Bourne
Member since:
2007-06-02

Everything that I have been hearing about Wayland is that is going to rock the butts off with dead light fast rendering and every desktop being pixel perfect. If this is really true, then desktop linux just have the potential to rise again (X is definitely a load of crap, specially when you have to kill it).

Come on, desktop devs. Start working your butts off right now!

Reply Score: 1

RE: So where's the thing...
by renox on Thu 25th Oct 2012 13:17 in reply to "So where's the thing..."
renox Member since:
2005-07-06

Everything that I have been hearing about Wayland is that is going to rock the butts off with dead light fast rendering
Then either you failed to listen or the one you heard was misinformed: Wayland ~= X.Org DRI2 extension, so if you use a toolkit which use the DRI2 extension the performance should stay the same (more or less: Wayland integrates the compositor and display in the same process: less IPC in Wayland)

and every desktop being pixel perfect.
With Weston, resizing Window should be "pixed perfect" (but resizing can be jerky), with KDE's Wayland server this is the opposite: resizing will be smooth but the content of the window can be "ugly".

As for the irrational criticisms of X: many times the blame has been on X even though the issue was with drivers, Wayland won't fix drivers issue.

Reply Parent Score: 4

RE[2]: So where's the thing...
by FishB8 on Fri 26th Oct 2012 04:13 in reply to "RE: So where's the thing..."
FishB8 Member since:
2006-01-16

Then either you failed to listen or the one you heard was misinformed: Wayland ~= X.Org DRI2 extension, so if you use a toolkit which use the DRI2 extension the performance should stay the same (more or less: Wayland integrates the compositor and display in the same process: less IPC in Wayland)

As for the irrational criticisms of X: many times the blame has been on X even though the issue was with drivers, Wayland won't fix drivers issue.


Bull crap. X11 is a protocol. It's a colossal fossilized terd from the late Triassic period of computing. You can dress it up all you want with fancy rendering extensions and the worlds best drivers, but the latency will still suck. A monolithic nightmare designed from a time before shared memory and dynamic linking has no business on a modern system.

Reply Parent Score: 2