Gnome developer proposes removing the X11 session

GNOME (and many others) have spent years telling anyone who has issues with Wayland that lead them to run an X session to report bugs, and has put a lot of effort into fixing those bugs. This seems like a reasonable next step.<p>&gt; This plan seems to The Reg&#x27;s FOSS Desk to be strong-arming people into adopting Wayland.<p>Or, more reasonably, to maintain less code for alternate paths in favor of fixing the issues that lead people to use those alternate paths.<p>Wayland has bugs. X has bugs. Fixes to one largely don&#x27;t help users of the other. Every bit of effort spent fixing a bug in X to help the fraction of users still using it is effort that <i>could</i> have gone into fixing the bugs in Wayland that leave people using X in the first place. A project taking a step like this allows it to consolidate those efforts.

As someone who used to be a diehard Linux user and supporter, and then switched back to windows after about a decade, this thread is a good reminder of why I switched back. I&#x27;ve been hearing about the year of the Linux desktop for... Years... And yet here are people who suggest I should put up with an incomplete, partially broken display server, because they don&#x27;t want to deal with maintenance of the old one. And in this thread, any complaint by real users who are missing features or have encountered bugs is met with a dismissal.<p>You know what? The equivalent of X11 in windows may be full of cruft, technical debt, poorly thought out &#x2F; &quot;unelegant&quot; design decisions... But it fucking works. I&#x27;m sorry, but I have other things to do than dealing with the constant churn of Linux desktop software.<p>I remember a decade ago when everyone was supposed to switch to pulseaudio, it was the greatest thing since sliced bread, its design was solid and future proof. Migrating from alsa did break everything and was a PITA. And alsa was still there! The fix for many problems was to configure something in the venerable alsamixer. Now apparently we need to migrate to pipewire. All I know is that upgrading broke my rpi4. I don&#x27;t care about the software, I just want my htpc to play a video with sound when I get back from work. I still had to run alsamixer and flip a few knobs to get it to work again. This is madness.

Wayland is no way ready<p><pre><code> - O proper screen recording support - broken screen sharing - No proper global keyboard shortcut - No push to talk support - Their developers are seriously crazy on their design decisions. - Several problems with multiple screens </code></pre> A proper refactor of X11 should have been the way to go and there should had been X12 with modern technologies

Go for it, I say.<p>It would be one of many in a long line of backward compatibility missteps they continue to make; and would help shore up my reasons for me to recommend other WMs, as well likely encouraging other developers to bring some of GNOME&#x27;s good stuff elsewhere.

X can easily support per-display DPI -- clients just have to eschew the legacy global DPI setting. The Xrandr extension knows the dimensions of each display in both pixels and millimeters from its EDID. Clients interested in making adjustments based on per-display DPI could simply use those values obtained from Xrandr. These values can be wrong, of course -- monitors have been known to lie in their EDID reports -- but they&#x27;d be wrong in Wayland too.<p>Of course, no one actually wants to do this work because there is a deep-seated intent to salt the earth where X once stood.

I understand the reasoning here, and frankly supported. I&#x27;ve been using X11 while having an available Wayland session because some applications are subtly broken on Wayland - discord has weird text input issues, same thing with Emacs, and Wezterm just flat out doesn&#x27;t work on Wayland with Nvidia GPUs. However, the slow breakage I&#x27;ve seen with X11 has caused me to start migrating. To explain, every now and then on X11 my screen will simply go black for a couple of seconds. It happens often enough where I&#x27;m no longer willing to accept in. And so thus I&#x27;ve moved to Wayland. And frankly, with a little bit of effort, I&#x27;ve found work-arounds for all of my issues - Wezterm works if you disable wayland, Emacs 29 works fine, and Discord is acceptable in the browser. And thus, I think that disabling X11 is a good idea because finally it would force people to actually make things work well under wayland, instead of being able to rely on X11 as a fallback.

This is going to leave so many people by the wayside. (Pun totally intended.) Late 2020, my jaw dropped on the floor when a developer from CERN showed up and said that X11 support was needed in ContainerSSH for their use case and then developed it. (The LxPlus service, which acts as a dev host for researchers.) I thought X11 forwarding was well and truly a thing of the past.<p>Yes, I know that waypipe is a thing, but it needs to be installed on both ends and I haven&#x27;t seen any mention of non-Linux support either.

With every year X is still in use more and more tech debt is being built up. It&#x27;s a big problem in how slow this migration is going. The Linux desktop community should have made this migration its top priority and have had completed it a decade ago. It&#x27;s sad to see how far behind the Linux desktop is compared to other operating systems.

It seems like this would effectively remove support for the BSDs which use X11. Am I missing something?

i’m working on a 240hz low latency game on linux.<p>currently i run on x11, either directly via startx or via dwm when developing.<p>i will switch to wayland in an instant if it demonstrably improves any metric i care about.<p>i continue to monitor the situation and look forward to improvements in either stack and in drivers.

Another case of GNOME living in la-la land. So glad KDE became kind of nice in recent years.

Reminds me of systemd: we &quot;modern&quot; developers despise anything that reminds us of &quot;traditional&quot; Unix, thus we need to rewrite it in such a way that is not only new, but actively punishes unwelcome users.<p>Then we will complain about &quot;embrace and extend&quot; while people try to replace their xdotool scripts and their perfectly working X11 setups.<p>Too bad for them: we don&#x27;t care about custom applications, we still aim to just steal users from Windows. And 2024 will be the Year of Linux on the Desktop.