This change proposal is not removing X11 libraries, so please discuss that issue elsewhere.
GNOME doesn’t have a distro, but only devs Wayland. Distros are dropping Xorg because DEs are going Wayland.
It seems chicken and egg , but where exactly did this begin?
I need to understand how everyone is ok with the desktop being slower. I was into Linux for performance since F22, and I’m convinced Wayland can’t be as-performant with stuff like libinput → evdev, and have years of experience major GPUs + games.
I can’t accept an inconsistent mouse cursor on a priority timer or -20 FPS on Dota 2 for non-visible Wayland improvements and I’m back into Windows. Who exactly is benefiting from Wayland, and who is supposed to benefit, because it feels like two different groups; any OS can render a desktop nowadays but I’m only aware of 1-2 doing it efficiently.
So where did everyone-into Wayland begin? I want to see the process that led up to now.
They do actually: GNOME OS. Desktops migrating to Wayland-based technology has been a long-time coming, and distributions have been aware of this.
This is a weird claim since the input stack is identical between X11 and Wayland.
In general, the benchmarks do not indicate this. To the contrary, it seems Wayland is much better for gaming than X11.
This has been a 15+ year thing, with GNOME adopting it 10 years ago. Feel free to trawl through history and use Wikipedia as starting point.
The difference between xorg and wayland in those benchmarks is minimal .
For those that were hypothesizing last week that the lighter-weight Xfce and LXQt desktops atop an X11 session would yield better performance than GNOME or KDE on Wayland, that wasn’t the case with this round of testing. For these Ubuntu 25.04 beta benchmarks while using the Radeon RX 7900 XTX graphics, the packaged KDE/GNOME Wayland sessions were delivering the best gaming performance out-of-the-box on Ubuntu 25.04 beta. Often times it was a tight race between these desktop sessions but there were no instances observed where using an X11-based session provided a measurably better experience.
You have your answer: the issues are specific with Mutter. And it’s possible that the GNOME Mutter developers aren’t much for playing video games where input latency matters, so they did not really prioritize it like KDE Plasma did due to it being important for Valve.
Honestly, I’m skeptical of you at this point. Intel’s drivers have literally been abandoned for X11 for most of the past decade (it hasn’t even had a release since December 2014!), while AMD only recently stopped prioritizing theirs. Admittedly, this doesn’t matter in the default configuration where we use kernel mode-setting, but then that’s the same as all Wayland environments.
You also are cherry-picking benchmarks to try to make a point that isn’t even relevant to you. Unless Xonotic is the game you play every day, it being an outlier isn’t helpful. And the differences are within the range of imperceptible at ~2FPS, so even if it was the game you play every day, it doesn’t matter whether you pick X11 or Wayland.
Finally, Michael Larabel has been doing benchmarking and actual qualification of Linux systems for more than two decades. If anything, he’s probably the closest to a per-eminent expert in the field that we have. He has far more credibility than you do on this point.
(post deleted by author)
The original proposal has been processed, and this spin off seems to not follow a common goal to solve anything but just puts forward assumptions against other assumptions to tackle/disprove each other, and it starts again to develop underlying aggressions (and new flags ). It seems to have lost its track anyway, and clearly does not tackle a specific question/problem anylonger. I thus close it.
@Espionage724 not related to the “topic closing” reasoning: I know you don’t mean it in a negative or insulting way, but please avoid sarcasm and irony: this can be easily misunderstood among cultures and people of different backgrounds. Especially when you refer to other people or their work, this can quickly (and accidentally) cross the line of our rules.