Live data from Hacker News

GNOME 50 completes the migration to Wayland, dropping X11 backend code

linuxiac.com

71–80 of 190 posts

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#71

Earlier quoted context omitted.

> x11 is in maintenance mode at this point and Gnome is not going anywhere True. But does not address the fact that Wayland is a bad solution to X11's problems, and that its architecturally broken from inception.

I don't know the implementation details but I can't really complain about the state of wayland today. It used to be annoying to get working many years ago (worse because I had a nvidia gpu). But today I drive a nigthly build of niri, run it by just spawning an dbuss session and everything works. Bluetooth audio, screen sharing, fractional scaling, no tearing, no font blurring. Every utility I needed has been created…

X11 is far more stable now since they stopped improving it! I haven't had a crash in 15 years.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#72
post #33

I don't understand how Wayland is becoming the norm when it can't even restore window positions yet.

Why does the display server have to restore window positions?

If you want that feature, then the display server doesn't need to be the one to support it when the display server lets applications obtain and control window positions.

Wayland doesn't let you do that, and it's a deliberate choice.

See e.g.:

https://wayland-book.com/xdg-shell-in-depth/interactive.html

"However, a deliberate design trait of Wayland makes application windows ignorant of their exact placement on screen or relative to other windows."

And: https://hackaday.com/2025/11/11/waylands-never-ending-opposi...

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#73

Earlier quoted context omitted.

> x11 is in maintenance mode at this point and Gnome is not going anywhere True. But does not address the fact that Wayland is a bad solution to X11's problems, and that its architecturally broken from inception.

I don't think it's true that anything is architecturally or fundamentally broken in Wayland (though if you disagree, I'm very curious what you think is so deeply broken). Most of the issues and slow adoption were because the core protocol was deliberately kept extremely minimal, and agreeing on all the needed extensions took a long time. Don't take it from me, but rather from KDE developer Nate Graham: https://pointi…

Window positioning is one that on its own is sufficient to make me ignore Wayland, as it means that without my own compositor with my own extension, I can't get a file manager that will behave how I want it.

Most people won't care, but for a number of us Wayland is stubbornly refusing to support functionality we see as dealbreakers.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#75
post #70

I haven’t booted into an X11 environment in maybe 4 years. Wayland has been fine (Fedora + Gnome, Fedora / Arch + Niri). I think this is one of those issues where hardcore users overestimate how much anyone else cares or will notice.

I used X when I started with Linux in my high school. When I finally stopped tolerating macOS almost a decade ago, I started with Wayland only, and never looked back. I even ditched Krita in favour of Gimp, solely because Gimp supports Wayland (from version 3, and on 2.99 before that). To this day, I don’t understand X, like at all. It’s all some super complicated pile to me. While I don’t understand Wayland either,…

Remember x11 was initially a client server model, where multiple clients could access a single x11 server. This brought a lot of complexity we don’t use these days

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#76
post #67

Earlier quoted context omitted.

"gnome-remote-desktop" does exactly that - providing (amongst other capabilities) a way to handle remote logins: https://gitlab.gnome.org/GNOME/gnome-remote-desktop

Remote assistance, NOT remote logins. It can be used as support when someone is already went to that computer, authenticated and has a full gnome session opened. So you literally CANNOT log in remotely :) If you are lucky, you can assist remotely to a session someone opened locally on that machine. And it's like that on any other WM. KDE also has a deceiving option in settings that suggests full remote desktop, while…

Please just click in the link, read the README! It offers: - remote assistance - headless multi user remote login - headless (single user)

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#77

What a strange title. X11 is still more popular than Gnome, and formulating a wish like a fact doesn't make it so.

Anecdotally, I strongly doubt this is true, although my environment is probably quite biased. I know a ton of people who use Gnome, some who use KDE, and I think roughly all of these people use them with Wayland. The standalone-WM users I know are also mostly on Sway or other Wayland ones. The only real X11 holdouts seem to be people using X11-only DE's, such as Xfce or Cinnamon.

Xfce is working on Wayland session support. It is working now with some limitations (limitations on what you can embed in the panel are all that's left, I think).

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#78

Earlier quoted context omitted.

x11 is in maintenance mode at this point and Gnome is not going anywhere. Gnome is used (and financed) by major distributions. Nothing new is being created with x11 and the people from freedesktop don't seen to be thrilled to maintain it. I don't think should change just for the sake of changing, but I'd start looking to migrate whatever you use that depends on x11.

I had assumed that XWayland is a drop-in replacement fo X11, and will be available indefinitely. I regularly write code which relies on a working X11. I have written a virtual machine which makes X11 calls to do 2D graphics and event handling, as well as applications which compile to the virtual machine code. If X11 and now XWayland cease to be available, not only would I have to rewrite large parts of my virtual mac…

Yes, XWayland is intended to continue to be available indefinitely.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#79
post #22

Earlier quoted context omitted.

x11 is in maintenance mode at this point and Gnome is not going anywhere. Gnome is used (and financed) by major distributions. Nothing new is being created with x11 and the people from freedesktop don't seen to be thrilled to maintain it. I don't think should change just for the sake of changing, but I'd start looking to migrate whatever you use that depends on x11.

The problem is that I find Wayland to be a lot buggier than x11. For example, terminal transparency using Konsole on KDE flickers for me. Its nearly there, but not quite. Maybe Gnome has no such issues?

I've never seen similar issues using a variety of terminals on Gnome, Sway, or Niri. Haven't used Konsole or Plasma, but I wonder if it's maybe a driver issue?

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#80
post #32

Earlier quoted context omitted.

Open source has never achieved user freedom. It’s achieved developer and very tech savvy IT pro freedom. If you can deal with command lines and debugging systems you are not a user. You’re a computer professional. If OSS wanted to bring freedom to users its primary focus would be radical simplification and UI/UX.

What nonsense, especially if framed in a such an absolutist way leaving no room for nuance. Millions of people are storing their data on self hosted or 3rd party run managed OSS services on multiple platforms. Sure, it is not all perfect, UX might be an issue here and there but compared to having to relearn using some proprietary app redesign every other year because some Product Manager needed a promotion, a lot of…

> Millions of people are storing their data on self hosted or 3rd party run managed OSS services on multiple platforms.

That's open source being used by developers to provide a closed service to users. Users experience it as an opaque closed service.

SaaS backed by open source is actually the most closed model of software, more closed than closed-source software run locally.

Post reply on HN