Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
XWayland is necessary to support the vast majority of GUIs that don't yet fully support Wayland (e.g. Firefox). Popup windows and context menus in XWayland behave badly, flickering, opening in strange sizes, and refusing to reopen within the same session. Seems to be best documented here and here. See More
Wayland has no drawing APIs. Instead, a Wayland client gets a DRM buffer handle, which is practically just a pointer to a graphics memory. Practically Wayland does not care how the client draws to that buffer, it only copies the client's buffers on the screen. The removes a lot of complexity (because Wayland just pushes the complex stuff to the other layers of the stack) and by making the clients responsible for all the rendering, they can be smarter on how they do things like double-buffering for example. See More
Most closed sourced drivers do not support the KMS/shared-GEM/shared-DRM technologies on which Wayland works. While this may be okay for open source purists, who only want to use graphic cards that have open source drivers available, it may not sit well with people who spend a lot of money for high-end graphic cards only to get some crappy 3D performance. Although it should be noted that NVIDIA has declared that they will start supporting Wayland, it may take years before Wayland fully supports most high-end drivers. See More
X11 is so tied up with everything in the Linux Kernel and userspace that it's become for a long time now the de-facto display server for Linux. A lot of things have been tied to X for decades now and it's hard to untie even if X has a lot of glaring problems. Because of this (and despite of X's problems), everything seems to work with X, from the WMs to the graphic drivers. See More
When using X, you can get information on any application that is running within any other application that is currently running. Things like position, size, framebuffer, which window has focus, etc. can all be accessed by any running application. With this in mind, there are countless customizations that can be achieved, things like changing the keyboard layout depending on the window that's focused, or creating a script that gets statistics for each key typed. The possibilities are endless. See More
The X stack is rather old and a lot of the things that have been added through the years feel more like hacks to make it work with newer technologies. This has made the X stack feel all over the place with bits and bobs everywhere. Making it a pain to maintain the stack in the long run. See More
Since Mir is being developed by Canonical to fit the need of the Unity DE and Ubuntu, on many different devices, from desktops to laptops to mobile devices and tablets. Because of this, Mir is great for Unity, in many different ways (security, efficiency, functionality, etc.). See More
Mir isn't bad. It just doesn't fit in the world outside Ubuntu products like Wayland does. Instead of Canonical choosing to use Wayland as their next generation display server they choose to go their own way, which does not contribute back to the community in any meaningful way, in that area. See More
Help millions of people make better decisions.
Each month, over 1.7 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.