Language Selection

English French German Italian Portuguese Spanish

The What Why and How of Wayland and Weston on Linux

Filed under
Software

Let's start from the beginning, because even though Wayland has been in development for over five years there is still a lot of misunderstanding of what it is. Wayland is a display server protocol that is intended to replace the X Window System. We've had X for 27 years, and computing has changed a wee bit in that time. Back in the olden days we had text terminals and every little pixel was precious. Now we have great honking graphics cards with more processing power than the servers and workstations of yesteryear, multiple displays, smartphones and tablets, embedded devices, and users who are not going to settle for colorful ANSI displays, but want complex 3D graphics. And why shouldn't Linux lead the way in graphics rendering? Are we not overdue for holodecks? And who would ever want to leave their holodeck? Though, as figure 1 shows, you can make some cool color images with ANSI.

The Evolution of X

X has been showing its age for the past 10-12 years, and has acquired a considerable cruft base in that time, to the point that it is more in the way than useful. You younguns might not remember, but back in the olden days of Linux we had to configure X manually, and it controlled displays, mice and keyboards. Yes, keyboards and mice. Why? Darned if I know. This is what I wrote in my awesome Linux Cookbook, published in 2004:

"XF86Config requires that you know configuration data about your mouse, keyboard, video adapter, and monitor. It takes you through setup line by line, asking questions until you're ready to explode. Most important are the name of your video card, the amount of video RAM, and the horizontal/vertical refresh rates for your monitor."

Rest here




More in Tux Machines

GNOME News

  • Do you like Windows 10 Look but Love LINUX? Here are Windows 10 GTK Themes for you!
  • A history about Gtk+, Vulkan and Wayland
    A few weeks ago, I was curious to test Gtk+ 4. I know it has some awsome features like OpenGL rendering, major cleanups and other hot stuff, but didn’t have the chance to check it out until then. I was mostly excited about Vulkan. I know both of my laptop’s graphic cards support Vulkan. It’s a hybrid Intel Broadwell G2 + NVidia GeForce 920M, although I don’t use the latter because Linux sucks hard with Dual GPU. Downloaded the latest Gtk+ source, compiled and… nothing. Immediate segmentation fault. Yay! What a great chance to get involved with the next major Gtk+ version development!
  • GNOME Developer On GTK4: State-of-the-Art of Toolkit Support
    GNOME developer Georges Stavracas has shared his thoughts on the state of the GTK4 tool-kit with the recent work involving a Vulkan renderer, including which also now works on Wayland. Georges Stavracas was excited to try the current state of GTK4 development but initially hit a segmentation fault. But after overcoming that, he was successful in running GTK4 on Wayland and the widgets being rendered by Vulkan. He commented on his blog, "May not be as exciting, since there are no new visible features but… damn, it’s Gtk+ being rendered with Vulkan on Wayland. It’s basically the state-of-the-art of toolkit support right now. Even better, the absolute majority of applications will gain this for free once they port to Gtk+ 4 series."

Red Hat and Fedora

Leftovers: Ubuntu

Android Leftovers