Xorg development effort slowing in favour of Wayland
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Actually this has been a core value of Unix design since the 1960s, and will be a valid goal in the 2060s.
Here in the Linux world we follow the principle of "don't break userspace".
Wayland violates this principle by rolling out a new protocol that breaks compatibility with existing applications. Just take the loss man, some people don't want wayland you need to accept that.
I'm not particularly interested in seeing this thread get repeatedly bumped by a non-slackware user who just wants to spout nonsense and argue. Can we get this thread locked, or at least moved to a more appropriate forum? Maybe general?
Looks like the discussion centers around a claim that some sort of specification that is not being properly implemented/obeyed. I don't see many people disputing that claim.
There is a pro-wayland side that apparently thinks setting wayland as the default is more important than technical issues because it "signals" to people that wayland is the future. It's not even a quantitative/qualitative dispute. Their goals have an evangelical component. ALL MUST USE WAYLAND. GLORY TO THE FUTURE.
There was this fun tidbit though if you want to test it out.
Code:
Running testsprite (with --vsync) on Gnome + XWayland, it throttles to 1hz for me when the window is occluded with both the GL and Vulkan renderers.
I like both Xorg and Wayland, but I favour Wayland due to the security implications.. I don't want to run unstable software either, or some kind of beta state software. So, while I've tested Wayland for about 5 years on or off, it was only with Slackware 15 I actually started using Wayland as the main option. Previous attempts (mainly due to KDE) felt unstable and did not fulfill the quality I was looking for, but these days Wayland (and KDE on Wayland) is becoming quite stable and functional.
It's not 100% there, but it's getting very close (as of Slackware 15), and it's mostly ready for everyday use. I expect this to improve further and make Wayland an obvious choice, most likely starting already with KDE 6. With KDE 6, they will use Wayland as the main option, and thus put most of their effort into Wayland improvements and polish, and new features might be prioritized for Wayland as well. But they will keep compatibility with Xorg, so people will be pretty much free to choose, and I think this will be an ideal situation for now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.