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 machine, but also rewrite all the 2D graphics code in applications. All so that I can stand still when the rug is being pulled from under my feet. I'm sure there are others in a similar predicament.
I may be naive about this, but as X11 just works, and has done for decades, it should require little to no maintenance, so why the need to withdraw it? I don't expect, or require, any additional functionality.
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.
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.
Nothing weird about it, it makes perfect sense with what you are posting. I find it weird that you react like that to a simple question. Just probing what kind of old software you use, cause it tells a lot depending.
It was weird because you implied (and still are) that it'd mean I was hanging on to old, superceded software that has adequate replacements. I'm not. So this is telling us more about your assumptions.
I'm using my own terminal, wm, and file manager. They use X11, and I have no interest in changing that, because I have no need to as long as X11 works on my hardware and that won't change anytime soon. Everything I don't do in a terminal, I do in a browser.
EDIT: To add some more context for why I have no interest in changing that:
1) my wm is 1568 lines of code at the moment. If anything, that is more than I'm happy with. With Wayland I'd need to write my own compositor. Way too much work even with reusing e.g. wlroots.
2) My file manager is more of a basic desktop launcher. That is fine, and intentional. I may add some features to it. But the reason I'm using that rather than any of the over a dozen options I've tested is that most of them either never had or have ripped out spatial features, and the ones that had some spatial features didn't act the way I wanted them to. I want Amiga-like semi-spatial features of being able to selectively snapshot icon and window placement ("semi-"spatial because traditional spatial would imply a single instance of a window for a given path; I just want default placement to be the same as last time I snapshotted it). Wayland on purpose refuses to allow that, and so I'd need to hack on a compositor or write my own to be able to support the most important feature to me in the file manager.
I'm not going to tolerate my usability being reduced just to switch away from software that does what I want it to, to software that offers me nothing new that I want and takes away features I do want.
I'm curious, what were you hoping to learn about their use of python 2? If you had specific questions, it would be helpful if you ask those, instead of trying to ask through euphemisms.
If it was maintained (security fixes and platform support only), but with no other changes, it would be a very tempting alternative to python3 for the many times API stability is valuable.
And wayland is in broken mode. KDE keep changing the default back to wayland after each update, and every time my linux systems are broken until I switch back to x11.
What is broken for you? At this point, starting from roughly KDE 6, Wayland has been pretty much flawless for me. KDE 5.27 was pretty much fine already as well.
Just installed fresh and logged in to Wayland. Sudo password stopped working. After fixing that it kept opening some window and refused to close. Even without those bugs none of the accessibility tools work.
Fractional scaling is awful on Wayland if the application relies on XWayland to work. Drives me up the wall having to find the various flags to force Wayland mode.
It would be sad if, after all those years, it was still missing anything significant. Maintenance mode sounds like a good thing, not something that makes me tempted to switch to some less stable alternative.
Reminds me of sites that required ActiveX to run arbitrary code on the user side when visiting a web site outside a sandbox. Turned out to not be ideal from a security point of view.
But I guess `ssh -X` users still miss those times...
I suspect you don't really guess that. There are differences between the two cases. For example, security threat models are a thing. Something can be secure against the threats it will face. I don't ssh -X into servers I don't already trust. There is no arbitrary code being run.
Do you have more specifics? I just tried it on my machine (Fedora 42, Plasma 6.5.1 Wayland, Konsole 25.08.2, Radeon 780M) and it seems fine for me. Does it only occur occasionally/under specific circumstances for example?
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?
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 and works quite nicely (e.g.: wdisplay). I can even play video games with HDR support.
I have a more stable experience with wayland today than I had with x11. Which to be fair was not only because of wayland but because desktop linux as a whole has made a lot of progress in the last years
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://pointieststick.com/2023/09/17/so-lets-talk-about-thi...
As such, anyone who tried it early probably had to deal with a pretty large amount of non-working stuff, but by now the platform is capable of most features people require and the biggest remaining bottleneck is that software needs to use these new APIs.
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.
That's fair! I believe that window positioning also works on XWayland, though, so running your file manager that way should still work with the rest of the system being Wayland (and Gnome has no plans to drop XWayland afaik).
I believe the main holdup is a desire for Wayland to be usable with e.g. VR interfaces where there is no simple 2d grid.
Out of curiosity, how do you want the file manager to behave? And did you write your own or are you using an existing one that works that way?
It's managing the desktop too, so I'm not sure that'd work unless running Xwayland in "rootful" mode, in which case I might just as well run X.
The VR stuff is a poor excuse - just fail on that scenario. Nobody that cares about window positioning will have an issue with that.
My file manager defaults to re-opening a window for any directory to a previously snapshotted location, like the Amiga Workbench did. And, yes, I wrote my own. It's a few hundred lines of of a quick and dirty Ruby hack talking directly to a pure Ruby X11 binding, which is anothe reason I stick with X - I can throw things together quickly for X. The amount of ceremony, or big additional dependencies, needed for Wayland is ridiculous.
The only file managers that run on Wayland are the weird "flat" kind with "is" that prevent you from doing anything that didn't match their poorly conceived use cases
I don't think I understand what you mean. Do you mean wayland is not usable with nvidia proprietary driver? I remember that being annoying but possible many year ago (with sway --my-next-gpu-wont-be-nvidia thingy).
But if you use really old nvidia gpu you can have a mixed experience with wayland. Which is a fair problem to complain, but you can't blame that on wayland and call that lack of freedom. That problem was caused by the lack of freedom coming from nvidia gpus and how locked down they are and how nvidia for many year has been hostile towards linux desktop.
The “what’s the harm” here is the systemd conversation all over again basically. If you pipe everything through a single point of failure black box users have already lost, when you combine it binary blob drivers that shouldn’t exist it’s worse. Linux is doomed in achieving its most important goals which are user freedom, not someone’s idea of pretty UI imposed at the expense of that. If that’s what users want they should buy a Mac. If you want to get locked out of your OS for eye candy we have that.
Where is this Wayland black box then? If anything, Wayland made this situation significantly better: the X11 server was exactly this 'single point of failure black box' you are describing. Wayland replaces this with a much simpler protocol with multiple independent implementations (notably Mutter/gnome-shell, KWin, wlroots-based ones such as sway, and Smithay-based ones such as niri).
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 OSS stuff is perfectly usable, stable and secure.
That’s because of extractive economics from tech not because of any failure or weakness of open source. If tech economy was in equilibrium open source would be massively popular. Polished alternatives are subsidies by extraction economics.
What's the substance behind this claim? It keeps on being repeated but I don't get what it's actually about. Is there anything proprietary about Wayland that I'm not aware of? What's the difference between proprietary drivers using X11 and Wayland?
The X Window System (X11) is a protocol with multiple implementations. Sure, the X.Org Server (Xorg) was the most popular by a huge margin, but there were quite a few others (e.g. XFree86, Xming, XWayland), though over time most were discontinued for one reason or another.
X11 and Wayland do differ in an important way: in X11 window managers (GNOME, KDE, i3, whatever) all sat atop the Xorg server; whereas in Wayland there’s only the compositor, so GNOME, KDE, Sway, whatever, all essentially include their own equivalent of Xorg (which could be fully integrated, or factored into a library, such as Mutter, KWin, wlroots).
There were plenty of those, including commercial ones.
It's pretty hard to find but ~25 years ago I was using Xi Graphics Accelerated-X which had 3D acceleration long before Xfree86.
Update: but yes I imagine it had some code from original MIT release.
For completely independent one you can have a look at WeirdX/WiredX, which was written in Java and even supported antialiasing and transparency for core protocol (something that Xfree86 people claimed to be impossible to implement).
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.