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.
x11 being in maintenance mode is the best thing that happened to it for my use case. It hasn't crashed in 15 years.
GNOME 50 completes the migration to Wayland, dropping X11 backend code
51–60 of 190 posts
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#52Earlier quoted context omitted.
Are you also still running python2?
What a weird question. I have no use compelling use-case for python2. I have plenty of use-cases for X, such as the fact that none of my software other than my browser has Wayland support, including my window manager.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#53Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#54X11 is not going anywhere. If anything it's Gnome adding another nail to its coffin
Really the only high-profile 'switch' in recent times I can think of is that Fedora promoted KDE to be first-class ('edition') alongside Gnome, instead of delegated to a more second-class spin. And while KDE is a bit more conservative in this regard, I believe that in the long term KDE also wants to go Wayland-only at some point.
Personally I did switch from Gnome to KDE some time after Gnome 40, since I quite liked 3.x but the UI overhaul 40 did wasn't really my thing. It also helps that KDE got a lot better in recent years.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#55What a strange title. X11 is still more popular than Gnome, and formulating a wish like a fact doesn't make it so.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#56One carousel there had 16K slides.
On Windows both Chrome and Firefox managed that fine. They scrolled from start to end and back without issue and you could see, I think, all the frames in my 60Hz screen.
On GNOME and X11 (dual boot, so same hardware) Chrome was fine but there were issues with Firefox. I was curious so I logged out and logged in with Wayland. On Wayland Firefox was fine too, indistinguishable from Chrome.
I don’t understand hardware, compositors, etc., so I have no idea why that was, but it was interesting to see.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#57What a strange title. X11 is still more popular than Gnome, and formulating a wish like a fact doesn't make it so.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#58I don't understand how Wayland is becoming the norm when it can't even restore window positions yet.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#59Earlier quoted context omitted.
For my part, I have no intention of moving off X11 for the next decade at least. The only app I use that I don't fully control is a browser, and the worst case fallback is to run the browser in a Wayland compositor that runs on X.
Are you also still running python2?
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#60I am sympathetic to people who have a working setup and just don’t want to mess with their configuration anymore. Unless you’re on OpenBSD, though, that ship has long sailed in most *nix distros (even “stable” Debian). Long-term stability is underrated but hard to achieve.