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.
Permalink for comment 539911
To read all comments associated with this story, please click here.
Wayland is glorious
by sirspudd on Wed 24th Oct 2012 18:14 UTC
sirspudd
Member since:
2010-10-13

I was a systems integration agent with Trolltech for 4 years. Every embedded device we got access to, with the exception of the Nvidia Tegra 2, had a completely shit accelerated GLES2 stack under X11. We had some vendors that will go unnamed, who promised us a competitive X11 drivers a couple months in advance, only to fail to deliver them for years. They were delivering drivers, they just performed revoltingly in comparison to their framebuffer fullscreen EGL compatriots.

In Qt, we had one multi-surface multiprocess driver for powervr hardware. The code was a nightmare to read, required tweaking on every powervr licensed device and was the closest thing to a production ready driver we had. People would be tied to Qt, QWS and powervr. This was a major blocking point, and on the consultancy projects we were involved in, a consistent point of failure.

Contrast this to Wayland, which one of our engineers integrated with the Qt Wayland stack in one evening. Any additional work to the common Qt Wayland stack benefits every device consuming it.

Nope, if you are trying to ship a device and don't need the Android marketplace, you can now ship something more professional on lower end hardware. This is relevant for IVI, set top boxes and other dedicated hardware platforms.

Reply Score: 5