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 540097
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: So where's the thing...
by FishB8 on Fri 26th Oct 2012 04:13 UTC in reply to "RE: So where's the thing..."
Member since:

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

RE[3]: So where's the thing...
by renox on Fri 26th Oct 2012 08:43 in reply to "RE[2]: So where's the thing..."
renox Member since:

Thanks for your so well researched arguments, I think that we couldn't have lived without them.
What was I saying 'irrational criticisms of X'?
Yet another example..

Reply Parent Score: 3

gfolkert Member since:


X11 is indeed a protocol.

You've mixed a TON of criticisms... that stem from implementations of CDE and old ways of handling libraries and memory management that have pretty much gone away in any Modern Build of X... (or that uses any of the recent re-factored source codes. Compilers now a day are a lot smarter than you obviously know.

Sorry you don't have a relative clue.

So, how long have you been actually *USING* X?

Edited 2012-10-26 15:23 UTC

Reply Parent Score: 2