I read this yesterday wanted to raise awareness for it - https://nocoffei.com/?p=451

It describes the regression in accessibility software for Linux from x11 to Wayland. Unfortunately, judging by the pace of protocols being accepted, I think we're years out from having a solution.

The most notable thing not working is Talon, which is a voice input system that lets you insert speech to text, manipulate windows, call scripts, etc, all via voice. It's software that works on Windows, MacOS, and x11, but not Wayland.

I think unfortunately right now the best bet is to, if you need the software, stick with X11 for as long as possible. An environment like i3 will probably be maintained for decades to come. Alternatively it might make sense to build some type of bespoke solution on top of a specific wayland stack, like re implementing what you get of talon in a kde plugin or via sway IPC. This seems viable to me but an incredible amount of work.

For people that need this, having to be a developer and build your own tooling in order to use your computer... it's not a future of Linux I'm particularly excited about. I don't want to leave people who need accessibility software behind, and I don't think any security justifications are actually real roadblocks which would prevent being able to serve these people. We have a coordination problem. It's less of a technical issue and more of an issue of getting people to agree on protocols which would let software like Talon work against the entire ecosystem.

I am happy the ecosystem is moving to Wayland, I think we're going end up in a better place. Wayland does solve some real problems for me (x11 screen tearing / frame pacing issues on Nvidia). I'm happy that KDE exists, it's great software.

I've paid for Talon beta access for years. I'm a heavy Talon+Cursorless user, and I'm dreading this move by KDE.

Ultimately I think this mostly confirms the danger of using closed source software (Talon). I have some personal accessibility tooling that works just fine on Wayland. It's KDE specific but it really wasn't hard to get working. And uinput works on a level below the compositor, so X11/Wayland are irrelevant.

My stuff is written in Rust, just like Talon. I'm sure it would take me an afternoon or less to copy it over to Talon... but the dev just isn't interested. I don't know why he's so dramatic about Wayland when there are people actively trying to help contribute. If you try to talk about Wayland on the official Slack, there's an autoresponder telling you to shut up about it. If this were open source, I or someone could just fork it and move on with my life.

Now I'm sure I could use Ghidra and hack the binary to add support, but I'm not excited about becoming dependent on software where the developer is actively hostile to my interests. It reminds me of the blog post from yesterday about the guy who hates his insulin pump. I'm still a Talon user but I hate it now.

I guess I'll be forced to move to XFCE soon? Where is everyone else moving to?

I also think it's unfortunate that Talon is closed source. You see this even in the support practices adopted, where all support is routed through a slack chatroom which doesn't let you view history older than I want to say a few months but might be wrong on the length of time. The author seems to want to force all support requests to go directly through him, presumably because it increases his income if he can create a direct connection with his users.

He's created an incredible piece of software, and that's entirely within his prerogative to do this, especially because him being able to work on it full time leads to more work going into the system. He's made the world a better place so I'm not trying to criticize too harshly. But it's also super unfortunate right, because now if I run into an issue with Talon I am unlikely to find a search result of someone else who has solved it, but rather I have to interact with the creator of the software in a silo'd manner that will not be useful to anyone else other than me.

Tthreatening to remove x11 support entirely (as the article alleges) is also unhinged, yes. We're in a situation in which the best accessibility software is being threatened to be removed from a working platform because the author is (justifiably) frustrated with support requests that he cannot fix because of the transition to Wayland.

I expect that sooner or later we're going to get a better solution to accessibility than Talon, I'm not sure exactly how but probably using local LLM's in a heavy way.

Hi, I'm the developer of Talon.

It's possible to do the simple compositor specific hacks from Talon's scripting system to give yourself partial Wayland support at roughly the quality I'd be able to provide myself, and I know of a couple efforts to do this.

The tentative plan for "dropping support for X11" is just to do one more public Linux X11 release, stop there, leave it available to download, and make it very clear what to expect when you download for Linux or run on Wayland. I plan to continue supporting X11 on the paid version indefinitely.

Most requests relating to Wayland on the Slack have not been offers to help, and way too many have ended up being unpleasant conversations.

I have a standing offer to reconsider my stance if someone can show the vast majority of the necessary APIs are available and well supported without compositor specific hacks.

For some of the other points above, consider me disappointed but not surprised.

A KDE developer commented: https://nocoffei.com/?p=451#comment-736

Quote:

>As a community, gather together, and successfully implement the entire API surface needed for Talon on GNOME, KDE, and wlroots,

Can you help find where we can work out this list?

An all or nothing probably isn’t going to work, but we can chip away at this.

There are definitely people who want to help.

This seems like it basically confirms ggp's complaints: You're not interested in addressing customers' needs, or giving them ways to address their needs themselves, and are instead taking a "if this doesn't meet my standards you're not allowed to do it" standpoint.

If slack interactions are so unpleasant, why do you direct all support through it?

Is there no way you could say "yes this is a hack, but we'll live with it for now until an actually good solution is available"? Maybe it could be added in such a way that it's easy to remove later (abstraction, encapsulation)?

I don't think any of your points reflect what I was trying to communicate.

> You're not interested in addressing customers' needs

I would love to support Wayland, but it is my position that it is impossible to "support Wayland" for Talon. I can only support a subset of the features and only on specific compositors, and it would be a lot of work.

> or giving them ways to address their needs themselves

As I said at the top of the message you are replying to, I believe today users already have the tools to address their needs themselves with about the same level of jank I'd be able to provide on Wayland. If this is a veiled hard line on open source being the only way for users to address their needs themselves, we have a philosophical difference that won't be sorted out in this thread.

> If slack interactions are so unpleasant, why do you direct all support through it?

That's a whole new sentence. I was specifically referring to the support requests for Wayland, which in the long tail have been more hostile toward me than is likely warranted.

> "yes this is a hack, but we'll live with it for now until an actually good solution is available"

The hack is switching to X11, which is fully supported, or working around it in your user scripts, which has already been done by some users for their specific environment.

Do you have your logic inverted? Wayland is taking away accessibility. You can't blame any isv for that.

And why should he be?

He provided a working version for Linux, he will continue to provide a version for Linux.

Wayland is deliberately sabotaging the Linux desktop by forcing it's way in, developers have their own time and schedule and do not appreciate being forced to throw out working code just because others want to reinvent the wheel. If Wayland did it right they had proper backward compatibility and none of this breakage would happen

Hi Lunixbochs, thank you for the comment. One of my take aways from the article was that you were considering removing the ability for Talon to work on x11 in the future. I appreciate the correction. I understand that you're dealing with a lot of unpleasant support requests (especially because people who have to use Talon are probably frustrated at having lost the ability to use their machine normally). I am sorry if I added to that, I do genuinely think you've made the world a better place.

Screentearing has been solved on x11 for a decade; if nvidia don't support TearFree in the driver, that's an nvidia issue, not an X11 issue.

Have had 4 1440p monitors connected at once for some time. Haven't had tearing issues.

"Alternatively it might make sense to build some type of bespoke solution on top of a specific wayland stack, like re implementing what you get of talon in a kde plugin or via sway IPC. This seems viable to me but an incredible amount of work."

I think that is the only way forward. There is no "Linux desktop". There is KDE, Gnome etc. and if you want to do "system utilities" you have to target one of those.

The point though is that there used to be a «Linux desktop» you could target before the Wayland transition. Fragmentation of an already small market segment is unfortunate.

It's KDE now. GNOME is the penguin that went to the mountains while KDE largely tries to be compatible with things that aren't KDE.

Sure. I use KDE myself. I actually like the Gnome default UI/UX more, but I'm really not fond of their "our way or the highway" approach when it comes to customization and interoperability. KDE feels more in line with the true FOSS "spirit", and after a bit of customization, fits my needs better than Gnome.

Things like input methods, certain accessibility functions, screen savers and similar things.

Huh? Fcitx and IBus both worked on GNOME and KDE as far as I'm aware. Now, Fcitx using QT and IBus using GTK helps them feel more native on KDE and GNOME respectively, but they would both work.

It seems to me that the issues on that page are Wayland-specific; anectotally, on my random X window manager works fine with Fcitx (except for Emacs, but that's probably Emacs' fault, not the IME protocol's).

No, that's a terrible idea. The right thing to do is design a Wayland protocol that gives you the access you need, get it accepted into wayland-protocols, and wait for all the compositors to implement it.

Yes, that's a slow, annoying process, but doing something bespoke means either you do the same work over and over for every compositor, or you only support one or two compositors. Neither of those is a good result.

It is way faster and better to implement what you want/need in the DE. Later, it it makes sense, you can standardize it.

It's not just accessibility software but really any customization. Like always the people making the decision to break compatibility and benefiting by being able to work on the cool new thing don't even pay a fraction of the pain inflicted by it.

The web solved this decades ago by removing customizability. That's why all your extensions can do is add context menu items and toolbar buttons at the right side, and mess with the page itself.

It’ll be a better place when Wayland (and by extension Gnome/KDE) stops becoming a cargo cult hell bent on destroying X11/Xlibre.

X11 is not dying because of Wayland, it's dying because it became an unmaintainable code mountain over the years since it has been tried to be converted to something which is not designed for in the first place.

...and I'm saying that as a person who likes X11.

That's Xorg. X11 is dying because Xorg is dying and Xorg is dying because all its developers quit and went to Wayland. There's Xlibre too but it's a shitshow. Any one of us here could continue Xorg maintenance but we're not.

I think Phoenix[0] is a promising project: it's an X11 server written from the ground up, with security and legacy feature removal in mind. It's basically what Wayland should have been IMO. We didn't need a new protocol, at most we needed a new implementation of X11.

https://git.dec05eba.com/phoenix

Plasma/Wayland Known Significant Issues[1]

No ability to save and restore positions of native Wayland windows

Real-fake-session-restored apps don't remember which virtual desktop their windows were on

No full-screen aspect ratio correction

"Spare Layouts" feature not implemented

"Per-application Keyboard Layout" does not work

No way to change the gamma or manually adjust the colors without generating or finding an appropriate ICC profile

Can't switch between multiple touch strip modes

No headless RDP

Opening files using command-line binaries in Konsole doesn't raise existing windows

Global Menu is not supported for non-Qt apps

Some apps' non-maximizable windows are broken with placement policy set as maximized

[1] https://community.kde.org/Plasma/Wayland_Known_Significant_I...

Also, I still haven't found a clipboard manager that works normally on Wayland.

And I rarely get it to recognize all my monitors first try. And it crashes semi-regularly.

Not sure how much is inherent to Wayland vs Gnome, but life is way better since I upgraded to Xlibre & Cinnamon.

Why do people only do this to the x11 guy?

I bet if you interrogated the wayland side to the same degree you would find similar, or worse. Afterall, who is more likely to be the bad guy? The corporations hurting linux by killing accessibility and interoperability, or the guy giving his spare time to save them?

Because he is a solo maintainer and has an outweighed influence on the software I would depend on. Plasma community is much healthier as a whole.

Find your criticisms of others and, if valid, air them. But surely, don't expect others to be silent in the face of harmful and terrible voices.

The Bluetooth integration needs work - missing features such as "never connect automatically."

Default lock screen experience still has a needless delay of 5 seconds when entering a wrong (even blank wrong) password, even on the first attempt.

+1 on the gamma controls

> Default lock screen experience still has a needless delay of 5 seconds when entering a wrong (even blank wrong) password, even on the first attempt.

I suspect that is not KDE's fault (or Wayland's) - it's probably PAM, which by default has a 2 second delay (+/- 50%). That default is extremely difficult to change, but you can configure it. See my instructions here: https://github.com/linux-pam/linux-pam/issues/778#issuecomme...

Also if you follow that issue you can see I've been trying to convince the PAM developers to fix it (by changing it to a 0.5 second delay, which is much more tolerable and no less secure). Unfortunately they have this weird idea that users want the delay, because it lets them recompose their thoughts after getting the password wrong or something like that.

Good lord that thread is a dumpster fire. Thanks for finding out wtf is causing this, it has annoyed me for two darn decades, but never enough to go as deep into finding the cause…

Bluetooth autoconnect configuration is a Wayland issue? I honestly would have never guessed. I always figured it was the responsibility of the DE or bluez service.

Well, seeing how systems are brute-forced and how much speed you can achieve today, these delays are more and more welcome on my end.

Authentication systems had lock out periods or increasing delays since decades. 1 attempt per 5 seconds and 12 attempts per minute would be equivalent for brute force. And 12 attempts per minute would be a very loose lock out policy.

However, it's a good starting point for any systems which might be user facing and reasonably secured by the network around the system.

There's such thing as bad defaults and starting too heavy-handed is starting with bad defaults.

In short, current default is a good compromise and a good default.

That sounds like tarpitting, or perhaps timing attacks protection, rather than anything wrong in the password check pipeline.

Pointer warp not generally supported so CAD programs fail in bizarre ways.

Although I think that there is FINALLY an actual spec for pointer warp. However, very few compositors support it.

The story of Wayland - restrict what applications can do in the name of "security" only to re-add the same thing in a compositor-specific way after years of pain inflicted on everyone. Wayland is fundamentally designed for the smartphone model and has no place on an open desktop.

I agree with the Wayland premise that having an old and hairy library everybody is afraid to touch is bad, but having those same capabilities implemented piecemeal and incompatibly by five (and counting!) compositor ecosystems in ways that aren't well-tested or well-integrated isn't better.

KDE on wayland doesn't let me roll up windows. I've been doing that for nearly 3 decades.

Also recently discovered KeepassXC can't do auto-type on Wayland for some reason. It seems to have a massive amount of limitations.

What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications.

Not saying that X11 is not broken and should not be replaced, but many Wayland's decisions harm user experience more than X11.

I have a virtual pinball cab with two (and soon) three displays. Wayland really makes life difficult here because the software needs to always put the playfield on one display, the backglass on another, and the "dot matrix display" window on a third. That's a big no-no with Wayland. Fortunately KDE has window rules as a workaround. Sway and Hyprland allow similar rules. Mutter on Gnome has no equivalent.

I'm guessing this would mess up other games as well, like multi-screen flight simulators or driving games. It would be really nice if user-trusted apps could be granted permissions on an app-by-app basis to allow absolute placement of windows for these cases instead of making us jump through hoops.

Yes, exactly. This security paranoia makes the devs' lives much more complicated. I have seen many apps turning off advanced features, such as screen color pickers. Automatation tools can be broken. Apps cant know their window positions, etc. You can see countless dev rants about Wayland and how it's generally unpleasant experience to work with.

Ah so that's why i cant use the chrome devtools color picker to pick colors off graphics editing software.

Makes me mad.

Ironically, the use case you described is exactly the sort of thing Wayland really excels at - if you're willing to write your own compositor. There's plenty of embedded devices that ship with an extremely simple Wayland compositor that does exactly this. It opens up one app, accepts as many windows from that app as it has displays, and renders one window per display. That's that. There's no super-secret desktop that could wind up accidentally displaying if the app crashes or gets its window accidentally moved about, because there's no desktop and no moving any of the windows. You just take output from an app and put that on the display, then send input back to it.

This is great. But this doesn't cover the general expectation of a desktop application.

I want application to know the screens, send windows to know positions etc etc. And this is now compositor specific. So some applications will know how to talk to the kde compositor to share the screen, or place a window at a specific position (very useful for so many things).

That's strange; you should be able to do that with the standard xdg-shell protocol, though I suppose it depends on the app's behavior. The app can tell the compositor which output to fullscreen each window on.

Alternately, if it's using layer-shell windows, those can also be pinned to a specific output.

If it's not layer-shell, and the windows aren't fullscreen, then yes... it's annoying. The xdg-session-management protocol will likely fix that in this particular case (at the expense of having to manually place the windows in the right places once, and then it can remember in the future), but that protocol has just recently been stabilized and of course no one supports it yet.

It's all so frustrating watching the Wayland folks reinvent everything, poorly, and after more than 10 years it's still not there yet.

>> It's all so frustrating watching the Wayland folks reinvent everything, poorly, and after more than 10 years it's still not there yet.

The whole project started in 2008, so almost 18 years.

If you use KDE, you can work around this because of the powerful feature set the window manager has for setting custom window behavior.

1. Right click the PIP window and then click "More Actions-> Special Window Settings".

2. On the window that pops up, click "Add Property", and add "Window title". Change the drop-down from "Unimportant" to "Exact match" (this works on Firefox because the window title is always "Picture-in-Picture", you might have to do something slightly different on Chrome if it does something different).

3. Click "Add Property" again, add "Keep above other windows", change the drop-down to "Force", and change the radio button to "Yes".

4. From now on, all PIP windows will show up on top of other windows.

It would definitely be nicer if there was some sort of "always on top" permission that applications could request, but it's not too bad.

Not too bad? A hidden procedure with ten clicks, which the user has to repeat for each web browser. And it may break at any time if the browser changes some details. Or if KDE changes. And it's specific to KDE, with no alternatives in most Wayland WMs.

All that for _one_ feature which works out-of-the-box with Xorg, and which Wayland removed for security reasons. From what I've seen, sharing the screen is another common feature which was broken with Wayland and is still painful.

I don't think Wayland's security model is very relevant to me since I have faith in Debian for filtering out rogue applications. So I have to reason to drop my smooth UX for a world of "not too bad" workarounds.

Look, I'm not a Wayland booster, I still prefer X11 most of the time, but this is really the way it should work. Applications should not be allowed to dictate how windows appear. That is the job of the window manager. Chrome's PIP is a stupid workaround for Windows and Mac because they do not have robust window management.

This is the issue with imposing semantics of the programming model on the behaviour.

User behaviour is the only _real_ thing, it happens. Everything else is in your head. If people in the real world use PiP, then it should happen. The programming model has to bend and change to support it. It simply does not matter if the window manager does something or the window does something.

Sure, there is always the security argument wayland folks fall back to. But what ever is the problem with making a one-time permission popup? "Google Chrome wants to open in PiP: allow | allow once.". Just expose the existing PiP code in the window manager as an API guarded with an `if` that apps can call. It's not even that much real work, just pure bikeshedding and architecture astronauting.

Permission prompts still only allow things that have already been thought of so we will see less innovation in the future. I don't think this kind of security model is needed at all for an open source desktop where we can enforce directly that programs respect the user instead.

Right right, and I'm not saying users shouldn't be able to have a floating window with video (or whatever) in it. I'm saying it shouldn't be Chrome making that window floating and always visible.

That expectation is really an immediate major UX defect. Most really good GUIs rely on tons and tons of subtle behaviors to work right (that is, to assist the user). That means - counterintuitively - that they need a lot of leeway in how they get to control their own windows to appear on the screen.

Ultimately, the screen is just an unbroken flat surface and windows are just a software level abstraction that has been tortured beyond hope and one that users shouldn't have to micromanage or understand deeply.

If an application needs something to appear at a specific spot in a specific way, the display manager needs to bend over backwards to make it happen or it's broken. Windows understands it. MacOS understands it. X11 understand it, but the community is working hard to throw that wisdom away.

I don't get it, if you're on google meet, and you want to make one of many videos PiP. How can you ever do that in the window manager? It has to be done in the application! You right click or click on the menu on that particular video, and click Picture in picture.

How the heck can the window manager do it?

The application could tell the window manager it wanted an always on top window. The window manager could ask the user if it should allow or reject and remember for this application or not.

That's exactly what I said... and also not how wayland works.

I cannot comprehend the way wayland folks think... quote from the xdg-pip discussion:

> To not make PiP windows effectively "always on top" and "on every workspace" dialogs - a terrible and sadly by applications used concept on X11 - PiP windows must be input-only, i.e. not receive keyboard, pointer and touch input

Like what the heck even? That is how pip windows are expected to work? And of course you want inputs on them? e.g to mute/unmute on a video call? Like these are use cases used daily by people. And its "terrible".

I also don't get it with the wayland people. It feels like they want to revert everything to a UX design that was getting old in the 90s.

How many buttons do you want on a window frame then? The typical 4 buttons already take a lot of space in the title bar. Not everything that seems like a good idea at first glance is actually good design.

I don't know man, everybody is fine with putting tabs, and searchbars, and a bunch of other shit in the titlebar, but god forbid we put one button that's actually incredibly useful.

alt + left mouse button anywhere in the window (maybe win button or something is default now).

using the titlebar for moving a window is extremely backwards and productivity killer.

that being said, I agree with you, and I think its an outright abomination to put the tabs in the titlebar, and its disgusting how crome and firefox by default removes the real titlebar

Alt+LMB drag is impossible to do properly, at least on Windows, because too many applications use that for their own inputs. There are some X11 applications that also use that (Blender?), so while it's cool when it works, it comes with pretty severe problems.

there might exist some programs that do it, but this might be why they changed default from alt to win key.

in either case, that appears to be the very extreme minority of cases you have to move a window

I've fucking had it with you people and your "design"

As many buttons as he thinks he needs, and as a compromise they can be disabled by default and enabled through settings. Instead your ilk will probably remove even those remaining buttons and replace them with some obscure movement command

No, I wouldn't. I'm not your enemy. Please don't antagonize people like that. It's rude and I considered not replying because of your tone.

I have a pretty strong oppinion that GUI basics must be simple but more advanced stuff (e.g. tools that trainee professionals spend most of their workday in) must not hide its raw power because the user can be expected to learn.

User interface essentials have to be understandable without mental gymnastics by default without appearing overwhelming. The overwhelming majority of computer users don't change defaults on most software and a shockingly big number of computer users deal with them only because they must, not because they derive joy from it. They don't engage deeply with these devices at all. So those defaults must be picked carefully to keep the UI approachable. This isn't the same as ripping out features or antagonizing power users that do bother to learn.

The job of the window manager is to manage windows if the user wants it to do that. However there's many situations in which users want the application to be in charge of window positioning.

Making a decision on the user's behalf doesn't sound very free to me.

>> Chrome's PIP is a stupid workaround for Windows and Mac because they do not have robust window management.

What are you talking about? It's very convenient when I watch video while I do some work or entertaining thing on other web page or app. It's fine if you don't want to use it but many people do.

Yes, it's fine, but it shouldn't be necessary. If Windows and Mac OS just had native support for always-on-top windows, you wouldn't need it.

I actually prefer macOS's PiP handling compared to other operating systems. In that it's a blessed concept that only goes to one corner of the screen and can be shunted out of the way easily.

Now imagine if that was designed properly, and you could just do that to any window, regardless of what the program thinks it should look like.

I use pinned (always above + on all workspace/desktop) quite often.

And to make it ergonomic I scripted kwin and set some shortcuts.

So yes, you can have any window PiP the way you like. But it requires you to do a long sequence of actions. Versus a single click for very specific PiP behavior.

Consider a window in a web browser tab. You could click the PiP button, which will pop out a tiny window, most likely already in a corner of the screen. This window is a mini video player. Your original browser tab stays untoucher, still at the same place in your web browser tab list, the rest of the tab still readable and scrollable etc etc.

Or, you could clone the tab. Move it to its own window. Locate the video. Put it in full screen. Un-fullscreen the window. Click on the pin button. Resize the window to the corner.

Same result, but not the same effort.

Note there is also a far simpler one: You can right-click the window on the taskbar and click Keep Above. This works for any window.

> I have faith in Debian for filtering out rogue applications

Sorry but all I can say to that is: lol

As for security, it's easy/possible to cut holes into a solid wall. But if your whole system is swiss cheese, you can't plug all of them in. Wayland is a solid wall where protocols are the means to cut new holes. Sure, protocol development is slow (at least their acceptance), but this is the proper way to do it.

And even if you have faith in your applications, do you also have faith in your data? Because it's a mostly C/c++ application set, one vulnerability is enough to make them malicious. And with the beautifully engineered default "GNU/Linux" userspace security model, the only thing a random script can't do on your machine is install a new video card driver. But everything else is under the same user and readily accessible with full network access.

Debian applications are not sandboxed so gimping the window system gains you exactly nothing. And yes, we can expect Debian to filter rogue applications.

One difference I notice in x11 gnome vs wayland gnome is firefox's PIP window is always on top on x11 even if I deselect "Always on top" (super + right click menu) in wayland that works fine and is even always on top by default.

I much prefer the latter, especially since I get the choice.

I tried this for getting windows to open where I want them instead of the center of the screen. Couldn't figure it out in five minutes. Though I'll probably try again, this shouldn't be a problem.

My Wayland pet peeve:

It still lacks keyboard LED control, so unprivileged X11 programs that use the Scroll Lock light as an indicator cannot be ported to Wayland.

This Plasma change is going to be painful for me. I wonder if there's an up-to-date list of Wayland shortcomings.

> unprivileged X11 programs that use the Scroll Lock light as an indicator

I didn't know such apps existed! What do they use it for?

One use case is a new message indicator. Unlike icons on the desktop, keyboard lights are visible even when a full-screen application is running, or when we're to the side of or across the room from the computer, or when the display is asleep. I depend on this for my daily communications.

Another use case is for keyboard macro utilities to indicate the state of layers, modifier modes, or multi-keystroke input sequences.

Others surely exist, since hardware lights can indicate just about anything, and are especially valuable where visibility is important. Even shell scripts can use them on X11, via the xset command.

assign yourself permission to the device(may or may not happen by default depending on your distribution), and you can actuate it in /sys/class/leds/inputXX::scrolllock/brightness.

probably also exists other tools to do it. this is then generic linux LED framework

I am aware of sysfs LED controls. They don't solve this problem, because access to them requires privileges (or permissions assigned by someone with privileges). It's not reasonable to expect that, just as it's not reasonable to expect a sysadmin to grant users permission to the keyboard device node before they can type anything.

Moreover, granting permissions on the sysfs nodes won't distinguish between a user who is logged in to the current virtual console and one who is not. Wayland correctly delegates keyboard ownership to compositors, but they have no way to expose the keyboard's outputs (the LEDs) because Wayland hasn't yet defined a protocol for doing so.

X11 has a protocol for this, and X servers handle it just fine. They account for different users and LED states on each virtual console, and do not require clients to have any special permissions. It's an area where Wayland fails to be a suitable replacement.

Isn't it also impossible to spawn a window in the last place it was open (or any arbitrary point) because you're not allowed to know or change where your window is by design? Nonsense like that makes me dread having to eventually use it.

are there really multiple confliction extensions? I thought they finally actually agreed on a protocol to do it?

Ah, for some reason I figured this was a minor bug that'd be fixed eventually. Wayland windows are never allowed to spawn always-on-top? Sort of lame.

If the logic is that it's the window manager's job to set window rules for this, fine, but in that case Plasma should probably ship with preconfigured rules matching the Chrome/Firefox PiP window.

I also find the lack of an Xlib-compatible macro API disruptive but I usually run an X11 session inside Xvnc for this purpose anyway.

I know nothing about the detailed technical differences between X11 and Wayland but with Hyprland for me the PIP is working as expected so I assume its not just a Wayland issue but specific to the window manager you are using? Maybe somebody else can explain?

As far as I know, there are multiple Wayland implementations. Which is also not good because it creates fragmentation and potential inconsistencies (some subtle differences in behavior, differences in bugs, etc). Maybe Hyprland solves the issue, but I don't want to use this DE just because it solves this particular issue. I have tons of other needs and preferences.

Isn't that usually how it goes? Wayland is a million little optional protocols, which in the abstract is a lovely idea but in practice means which things work depends on which grab-bag of features your compositor supports.

It's a bit like the web. You have a pretty slow moving list of "protocols" that are well-supported by everyone, and some "new experimental" ones that are only supported by one or two.

Gnome has a "Always on Top" toggle for each window. I imagine there's a protocol for an application to set it by default but the OP's window manager might not implement it or there might be an incompatibility.

I can't speak for Gnome, but KDE makes it pretty easy to create rules that apply automatically to any new window that meets whatever arbitrary criteria you set.

That's terrible. That's an "unbreak my software" preference. User's shouldn't have to mess with that; things should just work in ways they expect, out of the box.

I disagree. With how KDE handles this, I'm not at the mercy of the software vendor's whims on what windows stay on top and which ones don't. I have complete control through a standardized interface that can even be automated if I wish.

Does it require a little more knowledge on the part of the user? Yes, but it's worth it because with that knowledge comes power.

I fixed this like this:

1. Right click PIP window 2. More Actions -> Configure special window settings 3. Add property -> Layer Force Popup

After this it spawned always in middle, I also added property Position Remember, so it spawns where it was previously. I have no idea if this is the best way to fix but worked for me.

> doesn't allow windows to stay on top.

Are you sure that windows that, without your consent, are allowed to stay on top and grab your input are a good idea? And spawned by Chrome? As if we hadn't already enough ad-ware, click-harvesters, and spoofed dialogs popping up everywhere!

I know there is a couple of legitimate uses for this, but the ways it can be abused are vastly more.

I think the sensitive default should be to block it, and allowing it should be behind some user's conscious action. Yes, it adds some friction to some workflows and it takes a bit to get accustomed to. But it doesn't deserve the label "security paranoia".

Are you aware that if software misuses the capabilities its given by the system you can choose to stop using that software?

You can't do anything about a compromised app or JS from a random website. I always find it weird when people attack Wayland's security model, more isolation is obviously a great idea, as demonstrated by supply chain attacks in the recent decade.

It's that Wayland's design, implementation, their attitude, and everything else about it is terrible. It could have been implemented without compromising on features or convenience by explicitly specifying minimalistic controlled side channels in their security model from the start, instead of shifting it onto ad-hoc implementations. And of course the windowing system is already too large of an attack surface. Many people are thinking about going full Qubes due to the current realities, while the others live in denial and call even window isolation "paranoia". Fascinating.

Turn off the web browser feature that allows JS in an advertisement in a background tab to globally grab your input.

Sure, browsers had three decades of adversarial testing to evolve into sandboxes, but what are you going to do in case of something like the xz backdoor in a desktop application? It's no longer a hypothetical in 2020s.

You're going to be hacked. There's no useful middle ground between letting programs modify how your computer works and not letting programs modify how your computer works.

Do you want to see the dancing bunnies? [Yes] [No]

Apple apologists keep making the excuse that Apple has to provide no side loading because if there was any single way to do it, all scammers would be making all grandmas do that. They're correct.

I can't speak for Chrome, but I can right click a Firefox picture-in-picture window, tell it to remain on top, and it does, no problem. I've been using Plasma Wayland for years now and this has worked for ages

There is some resource leak in Chrome / Wayland combo, I mysteriously run out of memory after few days of keeping several Chrome windows. On X11 Chrome can keep going pretty much indefinitely

I definitely have to right click on the window in the taskbar and select Always Keep On Top with Firefox on Plasma Wayland. Not too big a deal but would be nice if it was something Firefox could just set on its own.

> Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top.

Wayland doesn't allow apps to force themselves to be always on top. I would argue that it is up to the window manager to provide this functionality at the discretion of the user. Kwin does this.

I would argue that software that I choose to install already has my discretion and should not be limited by the windowing system in what it can do.

I think the KDE developers in particular have done a great job of pushing Wayland forward and getting features that people want and need added as new protocols. KDE feels a lot smoother and more responsive when using Wayland than when using X11, and by this point most stuff has been updated to work properly on Wayland so I don't notice any breakage or missing features in day-to-day usage.

> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations, and brand new exciting features throughout Plasma.

I think the blog post would have been better if he had some specific examples in mind that he could have shared here.

When I upgraded from Debian 12 to 13 on my personal laptop running KDE, I knew that the switch from X11 to Wayland would happen and was braced for all kinds of issues, like every other time I tried to switch to Wayland in previous years.

Instead, I could tell literally no difference. Multiple desktops works fine, scaling works fine, screen capture works fine, old apps work fine, literally everything works just fine.

Good job, KDE team.

On the other hand, I recently installed a system with debian 13, and it was really easy to distinguish between X11 and wayland sessions: if the session displays a plasma desktop, it's X11, if it crashes on login, it is wayland. YMMV if you try to switch to wayland.

I upgraded to the latest PopOS with Cosmic running on Wayland.

Honestly everything just worked, but using it made me so nauseous. There was some latency somewhere, never figured it out. Running Cinnamon on X11 now. I did read some suggestions to improve latency but I have PTSD so it's going to take a while before I try Wayland again.

That’s interesting. I have the opposite effect—X11 always had jank and latency, to the point that it drove me to windows for a couple of years.

This is with multiple monitors on Nvidia’s, all of which support vsync. Disabling that did help, but why would I want to?

Wayland, currently, is butter smooth.

It's faux smoothness caused by the mandatory vsync. There's several frames of delay in Wayland which apparently you're not sensitive to

I've found Cosmic to be rather flaky, sadly (I'm rooting for it to succeed), so the latency issues may not have been Wayland-related.

Both KDE and GNOME seem to run very smoothly on Wayland.

You might have an older GPU that doesn't work with wayland like me. My Radeon HD5870 also won't do Vulkan and anything wayland has never worked properly for me.

I'm not questioning what you are saying, but Wayland's only requirement is DRM, which is a Linux kernel capability that is supported for basically everything that you can push some sort of display cable into. It's for buffer management, and X was also ported to use this API.

Unless you have proprietary X server blobs, you have mostly the same low level route in either case to display stuff, so it's on the exact compositor you have tried, not on the wayland protocol.

I agree, it should work. It just doesn't. I haven't had the time yet to figure out why it doesn't because everything is fine on X11.

I have the same issue using either an older AMD card and an RTX 3 series card. Both are fine with X11.

Then something os wrong is in your machine. I'm just using KDE on Wayland on Debian 13 and just works fine.

Probably didn't even bother to diagnose the issue. It's hard to tell if it was even wayland related without logs and some digging. But lets just blindly blame wayland cause new thing bad!

Log in using wayland -> no desktop. Log in using x11 -> desktop. Clearly it's "wayland related" even if whatever root cause it is is something you wouldn't consider directly attributable to it. Logging into a graphical session is something that has just worked out of the box each other install on whatever random hardware I've used for many years. How is that classified as some nitpicky "new thing bad" complaint?

Well, it's like new car doesn't start but you have forgotten to put fuel into it, and now blame the car.

This is Linux desktop, like if you have never had a black screen before then I'm not sure what you expect. One culprit could actually be the home .config/.cache folders that have all kind of sh*t accumulated (like why do we still do it this way? It's horrible), so I usually rename them and try again to see if this is the problem behind the scenes.

Well, if I never had to put fuel into my old car then this would be a step back, no? I'm not a stranger to troubleshooting, and do a lot of it already, which occupies my energy and time for troubleshooting. I use Debian stable for a reason. It's mostly that if I didn't go looking for a new thing, it doesn't provide anything new that I want, it removes old things that I want, and it doesn't work without troubleshooting, why do I want this thing?

This specifically isn't the biggest issue for me right now because I use this machine mainly over ssh, but if I eventually can't do x-forwarding, RDP, or log in manually without finding some fix, that's a lot of extra work and lost functionality.

Blame on Wayland is absolutely justified here. If you force changes onto others its up to you to make sure you're not breaking things.

I think I noticed lower latency, more consistent frame pacing (recent-ish improvement in KWin) and a more "solid" feel because everything in a frame is synchronized. On X11, you can have things like border and contents of a window not matching exactly while resizing. An early principle of Wayland was "Every frame is perfect", which is clearly reflected in how e.g. window resizing works.

When switching to Wayland I lost a lot of custom interactions. I’ve learned to live without them but I still miss them.

For example I was a big user of devilspie for placing windows in certain locations, on certain desktops, marking windows as sticky, or marking them as different types of windows.

I am still a heavy user of pidgin (I know I know but I’ve even written my own protocols for it). I really liked being able to place it in a certain position as a certain size, mark it as sticky, put it below anll windows, and mark the buddy list as a utility window. This places in the background, removed borders, and doesn’t include it in alt-tab or window list when you do the expose type of thing. Then I had a global key binding to bring it to the front of all windows or drop it back of all windows.

As far as I know, none of these paradigms even exist in Wayland and I’ve had to deal with less useful options or completely change my interactions which is unfortunate.

my experience us sadly the opposite. when I'm recording gameplay with OBS with x11 and xfce I have roughly a 7-9ms frame render time and with Wayland and any desktop env it creeps up above 16ms, which means I can't get a solid 60fps.

in all other cases other than gaming and recording, Wayland has been a delight.

The 940mx on this laptop doesn't support hardware video encoding, so I'm basically forced to run everything on CPU. I do also stream so it's definitely a nice to have.

I could run the game on the GPU and leave more CPU for the desktop and encoder, maybe I'd be able to record and play on Wayland that way, but there's some additional drawing latency if I run the game on the GPU, the frame buffer gets sent back to the CPU before it's drawn on the display anyways.

As it's rhythm games I mainly play (ITGmania, Stepmania fork), the additional latency for getting the picture out on the display it's not really working out great for me.

With X11 you don't have to care about what wm/compositor you're using to choose a screen recorder.

For the records, Debian 13 Gnome with Wayland works as well as with X11. The only reason I'm still using X11 is that backlight control doesn't work anymore with my old laptop (it did with Debian 11) and X11 can work around it with gamma correction and Wayland can not.

Messing with colors looks like gamma correction and dimming in hardware is the backlight control that does not work anymore on my laptop.

I don't remember why gamma correction didn't work for me Wayland but I'll give it another try next year, maybe it got fixed by then. X11 is working perfectly well and it always did for me.

I recently installed Kubuntu 26.XX on my desktop, was worried about having to use workarounds and giving up on fractional scaling to use it with my NVIDIA gpus (previously had to do this), but was also pretty surprised that it has been smooth sailing.

Yeah agreed. I switched to kde from gnome a few months back, and it's amazing how much better it's been in a thousand little ways.

I mean… gnome has always been worse quality than KDE. I'd say even when the awful KDE4 came out was still better than Gnome3

> I don't notice any breakage or missing features in day-to-day usage.

I use it on a touchscreen and the on-screen-keyboard crashes several times a day.

I would not say it's fully ready.

> KDE feels a lot smoother and more responsive when using Wayland than when using X11

Or, the X11 code is more complex and they prefer Wayland because it is simpler. Fewer features. Is it a surprise that wayland would be faster, if it does less?

> by this point most stuff has been updated to work properly on Wayland

Really? Strange how comments on reddit do not confirm this. Admittedly they did fix various issues. I don't see how this equates KDE on wayland being better than KDE on xorg - even more so as they abandoned xorg now, as that blog post shows. So how can this even be compared?

> I don't notice any breakage or missing features in day-to-day usage

Why is this contradicting what others report then?

> I think the blog post would have been better if he had some specific examples in mind that he could have shared here.

David and Nate are all about marketing buzz. I am hardly the only one to have noticed this already. Then again if you are too critical of them on reddit, you get banned. I found that out when I critisized Nate's obsession with money. :)

Though, I am hardly the first with that either:

https://jriddell.org/2025/09/14/adios-chicos-25-years-of-kde...

Edit: Interesting, the above URL no longer works. Guess jriddell took down his old criticism some weeks ago. Anyone able to show how the old content looked like?

Edit2: Hah, found it - wayback machine is so great; people would have thought I made the above URL in error, but here is the old content from last year:

https://web.archive.org/web/20250917012150/https://jriddell....

> Strange how comments on reddit do not confirm this.

That is because people who don't have a problem don't think about this and so don't comment. Many wayland users don't know. I think I switched this machine I'm using now to wayland a while ago but I don't remember, and maybe it switched back in an update and I didn't notice (which is the point, I know I switched at some point and I couldn't tell the difference - which is how it should be)

Perhaps the Wayland code path does not have to do thousands of workarounds with an ancient API made thinking on remote graphical terminals.

I empathize but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11.

I'll be sad if that is still the case when 6.8 rolls around as then I'll be hunting for another DE.

Well, there's SonicDE, but like many such projects it's probably maintained by reactionaries which introduces its own suite of issues around security, code quality, and "will this be maintained in a year, 5 years?"

Is that "reactionaries" in the "we object to certain technology decisions" sense, like the anti-systemd crowd, or in the "software compatible with our political views" like the xlibre project?

A quick search (in which I found no evidence of heated controversy) suggests to me that it's the first one.

" anti-systemd crowd "?

I suppose you're from the " hop onto the bandwagon no questions asked crowd " then.

As far as I know right now, the first, but there's significant overlap. The suckless folks, for instance, have documented fash tendencies. The fact that SonicDE's stated mission is to preserve X11 support is itself a warning sign.

>The fact that SonicDE's stated mission is to preserve X11 support is itself a warning sign.

Why is it a warning sign? Sounds very useful to keep X11 support for machines that have no good video acceleration like office computers or stuff relying on VNC protocols.

I stick with LTS releases so last honest attempt would have been on a Kubuntu 24.04 LTS system.

What is a compositor - thing that actually draws window content on the screen? Whatever KDE provides?

Edit: To be fair to KDE/Wayland, the Wayland Kubuntu 24.04 experience was vastly improved over Kubuntu 22.04.

You are using a 3 year old Plasma release (5.27). Give the latest Plasma a try and you should hopefully be positively surprised.

They've made major strides in the last two years. Give the next LTS a shot and I think you'll agree.

Just works out of the box without problems in Debian 13.

The only issue that I noticed it's with screen scaling doing weird things with OpenOffice.

I'm not denying that X11 has known security issues. However, I don't tend to run untrusted random gui applications on my system so that factors into the risks I'm willing to accept.

Thank goodness I never jumped back on the KDE bandwagon once KDE4 stopped sucking donkey balls. I just went with xmonad and the few apps I actually use.

As someone who shipped my fair share of critical production features, I find this plan raising my eyebrows somewhat. Disabling a feature AND simultaneously removing the codebase for that feature almost never ends well. There will always be some use cases that people haven't thought of.

In serious projects (read, your career is at stake) a much better strategy is to first make the feature unavailable by normal means while still allowing a workaround (in this case, for example, PLM could remove X11 option from the menu but still allow X11 sessions when some magic environment variable is set.) That would give people an easy way to get the old functionality if something is critically impaired for them. And only then, once we are confident that no massive unforeseen issue has surfaced, can the codebase be removed.

> a much better strategy is to first make the feature unavailable by normal means

They started doing that in early 2024 with the release of KDE 6.0 by enabling KDE Wayland by default. The Wayland-only change won't happen til 6.8 which will be an early 2027 release.

https://pointieststick.com/2023/11/10/this-week-in-kde-wayla...

> And only then, once we are confident that no massive unforeseen issue has surfaced, can the codebase be removed.

Yes, that's the current step they'll be at with 6.8.

The problem with that strategy when it comes to desktop software is there's no way for the developer to know what the user has done (unless the software phones home, which is a no-no when it comes to privacy-respecting open source software).

If it's a SaaS API or a web application, the developers can look at access logs or analytics to determine what endpoints and features are being used, and when users need to go back to the deprecated interfaces to get what they want.

There's no way for a KDE developer to learn "$NUMBER users went back to X11 because $FEATURE is missing in the Wayland version".

(Of course they can ask their users, or hope that users file issues on the bug tracker, but things will definitely fall through the cracks via these imperfect communication channels.)

I really miss the ability to swap out KWin for a tiling window manager. I'm currently using Krohnkite and it's OK, much better than nothing, but after having used a real tiling window manager the difference is just too jarring. I physically need a desktop which is usable as much as possible both with the mouse and with the keyboard so I have to switch as rarely between the two as possible. Plasma on X11 with a tiling window manger was the perfect combo.

The solution would be either for Plasma to do something like River did [1] and separate compositing from window management, or for Plasma to make it possible to use Plasma widgets in other compositors. As it stands now I either have to make do with Krohnkite or go down the ricing rabbit hole with with River and Quickshell.

[1] https://isaacfreund.com/blog/river-window-management/

Have you tried LXQt? It made things easy for me when Plasma 6 broke a KWin script I was using to improve the multihead experience.

Been using Linux as sole OS for 25 years now. I will stick to X11 no problems, I am sure it will be just fine for my usage. When we thought Gnome 2 was gone, MATE fork appeared, X11 will be there for a long time. I am also going through the struggle of porting a software I maintain (github.com/edumucelli/docking) to Wayland and it is awful: "this compositor do this part, that one does that part, no compositor does this :shrug".

I have a feeling xorg will still be there, when devs have moved on from wayland to the next new thing.

I'm still thinking wayland will be like pulseaudio. Going from "the future" to "the past" without ever being "the present".

I went from ALSA to pipewire. I tried pulseaudio but it never worked decently.

Sadly, recent GNOME versions introduced a hard dependency on systemd and can no longer be used on systemd-free distros. This is the kind of problem that the anti-systemd people had in mind back then when debates about systemd raged.

I'm sorry, but are we still going on about this? I love a good debate as much as the next guy, but being able to just have one interface (systemd's) for all services and having a more-or-less consistent language really helps.

At this point, it's simply a bit too late. I'm sure in the early days it was still a choice, but when you want prepackaged things, you get systemd.

You could also just use one system (Windows) for everything if you wanted. Some of us decided to use Linux because we want things to work how we want and not how some bigshot decides they should work.

Yeah and you can choose to use a 32 bit system, choose to delete half your kernel, and various cool things, none of which need to be SUPPORTED by others. There's nothing that should say that a maintainer must take into consideration every possible choice the user might make, and then support it.

There is a difference between things being supported and the absence of things not being supported…

If you truly want things to work the way you want, you should develop your own OS.

But if you are using software that other people provided to you for free, I think the developers also get a say in how things work. And in case you didn't notice, most open source licenses will tell you that they don't provide any kind of warranty.

It's Linux bro, we absolutely need to have 500 different options for every single thing. Doesn't matter if every option sucks, diversity is above everything! /s

There are some truly special people among Linux users that think diversity in init systems/libc implementations/etc is a good thing for a general-purpose desktop. They don't understand that people just want stuff to work, and developers don't want to support more than 1 init system (or other trivial thing) for their package.

Success of Linux on the desktop is fundamentally incompatible with diversity, but unfortunately not everyone gets that.

> Success of Linux on the desktop is fundamentally incompatible with diversity, but unfortunately not everyone gets that.

The vast majority of "server" distributions now use systemd as well.

Anyone on the most recent LTS Kernel (6.18) with an older nvidia GPU will not have a good experience on Wayland. I have two machines with Pascal GPUs and:

- The nvidia binary driver is shit with Wayland

- The nvidia OSS driver does not support Pascal GPUs.

- Nouveau got a bunch of stability improvments in Linux 6.19, without which Wayland crashes roughly weekly.

You can get a stable system either by using the latest kernel+nouveau or:

  MESA_LOADER_DRIVER_OVERRIDE=kms_swrast

but performance is rather abysmal.

My touchpad still works like shit on libinput (which is the only input method available on wayland).

I guess in a few years I'll need to patch it and carry my patches forever. Yay progress!

> This particular model is used because it has hacks in libinput codebase to enable smooth scrolling with wheel.

Yet another glowing endorsement for libinput.

> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations [sic], and brand new exciting features throughout Plasma.

I wish they would have listed what some of those features might be.

I’m not surprised they’re not nailed down. But I’d appreciate seeing a “we’re looking at X or Y or if Z is now possible” kind of thing.

The maintenance and performance stuff is good, but it’s not exactly end user stuff. Yeah you benefit but it’s less obvious.

I don’t follow this stuff closely so personally I have no idea what kind of Wayland only features could exist that couldn’t before.

One nice feature is trackpad gestures. x11's trackpad gestures are awful, but on Wayland you can have the 1:1 multitouch that everyone loves.

Is that a British spelling? Oops.

Honestly my computer gave it a red underline so I decided to do that. I didn’t think about it harder than that.

If I recognized it like “colour” I wouldn’t have.

It's fairly common for us to use "-ise" instead of "-ize", but having now looked at Wikipedia on the subject, it appears that I incorrectly thought of "-ize" as an Americanism. The "-ize" suffix predates "-ise" - it comes from ancient Greek/Latin whereas "-ise" comes from French.

And the “[sic]” is followed by an incorrect attempt to form a conditional. Both problems arise from the same cause.

>judgment vs. judgement

In British English "judgment" without the 'e' is generally only used for talking about judicial rulings, whereas most other uses of the word contain the 'e'.

I wouldn't say its "plain impossible" with X11, but its significantly easier on Wayland because its a far simpler design that aligns better with the graphics hardware, we're sending surfaces (or pointers to them) with metadata to the compositor, not drawing APIs.

That already works with Plasma Wayland. It's still a bit finicky to make it work with things running in XWayland (Windows games primarily) but it's getting better.

Which is odd, because X11 has all this visual and depth stuff leftover from the days of 1/4/8/16-bit displays, and mixing windows of each type on the same screen. You would expect it to be capable of representing 48 bits just as well.

I've been using Kubuntu for the past 12 years without any X-related issue, and have and am actively working on stuff that requires it. I guess it's time to switch to another DE.

Most people are not you. A small minority do things that really need X. However there is good reason to say that the things that really need X are things you shouldn't do anyway.

Meanwhile there is a slightly larger minority that need things that cannot be done in X.

For the vast majority of people they cannot tell the difference, either works just fine. If there are issues they are tiny things they don't notice until somebody points it out - and then they forget in a few days.

> the things that really need X are things you shouldn't do anyway.

I had just finished reading the link in the first post and, frankly, I'm grateful for.the insight it gives. I think we all should have more perspective than what we have around things that we take for granted. Wayland itself would be better if its own devs had done the same.

https://nocoffei.com/?p=451

> Meanwhile there is a slightly larger minority that need things that cannot be done in X.

List of things that cannot be done in X:

That's not actually a good thing. General purpose programming languages as configuration file formats also give you "can do anything"; but when it comes time to try to improve or update the Python package ecosystem, you're forced to break backwards compatibility. Or give up on whole classes of improvements, because you can't constrain package behaviour at all.

Yes, I do. And X11 is the "Or give up on whole classes of improvements, because you can't constrain package behaviour at all."

Or really, give up on anything that might change behaviour, if you don't want to break back compat.

The only improvement is isolation, which I don't care about since apps can all access my clipboard and my home anyway.

Interesting. But the only thing I would miss, is something like a settings menu. Or do you really expect me to fiddle around in config files to configure basic stuff like wifi? Or am I just stupid? Oh wait, I could use claude for that....

Thanks for the recommendation, but "nmtui" is also the most Linux answer you could have given me :)

And it completely misses the point. Yes, there’s a lightweight tool for everything, but the appeal of KDE is that I don’t need to know. It mostly just works, is extendable and configurable.

But i also understand the appeal of staying minimal. The thing is, i want some kind of middleground: I want a simple tiling window manager. But i also want to easily install and configure stuff without falling back to the command line.

Maybe it's also brain damage of using too much Windows (with wsl). But there I have a different problem: It's easy to install and configure stuff, but it's everything else than minimal.

XFCE. Supports the tray plugins, has GUI settings, I don't ever have to use the CLI to configure it (actually... I'm not even sure how I would...).

I have jgmenu mapped to F4 but I never remember to use it. I usually just CMD+P and type what I need.

I can see the appeal of KDE - I just got fed up of things breaking when I did mandatory upgrades for security. I don't have to choose between stability and security. After 10+ years, I would find it harder to go pecking through menus for what I need when I can just type it.

Wayland is great and I generally prefer it, but it's worth keeping X around for KDE Plasma I think. Things like remote desktop are nicer on X, X is much easier to use on Android compared to Wayland, etc.

in my mind unfortunately this basically destroys KDE's viability as a gaming platform. SO many older games just do not work properly unless run under X11 (hell, some newer ones too). XWayland is good for everyday applications but for games in my experience it too often falls flat.

As someone who likes games from various periods (from Ultima IV to WH40K: Rogue Trader), I haven't ran into many games which do work on X11 and don't work on Wayland. Though I don't really have any of the old Loki games (I believe there was a port of Unreal Tournament?), so I might be missing out on the specific games which really lean into certain X11 features which XWayland doesn't support well.

I'm very surprised to hear that. Ive seen some issues with apps using Xwayland, mostly scaling related. I dont recall ever seeing an issue with a game running on Xwayland. Its also how the Steam Deck runs all games.

You can try running in gamescope, although in my experience Wayland has not been an issue. The few games I have that gave me problems in Wine didn't work any better when using an X11 session.

I was under the impression that the Steam Deck runs under KDE Wayland? I wasn't aware of it having video game support challenges due to Wayland.

I can't say I've run into issues running games under XWayland, but I have only been using the Wayland session for a couple of weeks now. The blocker for me was Discord (you wouldn't get messages on your phone if you were afk because the idle detection didn't work in Wayland), but the devs there seem to have finally fixed it.

funny you say that, given that the SteamDeck (the largest/most popular Linux-based gaming console) runs on KDE on Wayland.....

I installed Arch on my old Mac few months ago, alongside Xorg and i3, they were what I was used to before I switched to Mac about 6 years ago. Back then Wayland was a mess, so I never even bothered to check it out this time.

However, few days ago my non-technical girlfriend wanted to use my laptop, I couldn't see her using i3 so I decided to install Plasma, a proper desktop environment. Lo and behold I couldn't launch it. After searching I found out I needed plasma-x11-session as the default plasma install now included just a Wayland session. I found this a bit surprising, so I did further digging and discovered a huge chunk of Linux desktop community have basically migrated to Wayland since the last time I was here. Very surprising I must say.

So I decided to try Wayland again; I installed Sway and was pleasantly surprised. My screen resolution was automatically calibrated, operations seemed to run more smoothly, my laptop's fan kicked in less frequently (don't know why), and I didn't need a compositor package to fix screen tear (bye Picom). But all these weren't the reasons I decided to stick with Wayland. You see, in x11 I've been having a persistent problem: playing videos from certain websites, notably Twitter, introduces noticeable flickers. I tried everything to get rid of this: media drivers, verifying GPU acceleration, calibrating refresh rates, nothing worked. When I installed Sway I decided to see if this issue got magically fixed, and lo! It was. Wayland has come a long way since I last tried it. Now that I mentioned it, I have just remembered I need to figure out a way to share screens on Google meets, at the moment I seem to be limited to sharing just the Chrome window.

I recently had opposite experience - I been using NixOS with X11+i3 for about 2 years and never had any significant issues beside some troubles with one Nvidia driver version, even most Steam games worked for me without any issues. But out of curiosity decided to give try Wayland+Sway. First Sway remind me that Nvidia GPU completely unsupported and probably wont work at all, but in really fix for that just to use some 'unsupported' flag to launch it. After that I found that displays fractional scaling only can multiply original resolution to bigger size so is no way I will able to set up my 3 different displays in way I would like. Then I found that Zoom app can't share display even if everything for that is provided and it thinks that sharing actually happen (it can share if used thought web-browser and it also some workaround with virtual camera thought kernel module and OBS). After that I found that Barrier app (that I been used to share cursor/keyboard between desktop&laptop) while has support for wayland it can't work with Sway yet and is no any real alternative.

For now I can deal with that stuff but it looks like more I use wayland more issues I see so not sure that I will able stick with it long term.

oh now I also has flickers with discord app

Interesting. From looking into it Wayland had issues with Nvidia, I thought that was already fixed? I admit, it is a bit of a hack getting screen-sharing to work; I've not really had time for it yet as it isn't a daily driver for me.

A huge thank you to the KDE team. Plasma is good (finally) on Wayland for me (AMD graphics, single hi-dpi screen). I finally switched over from GNOME and I am happy with the experience.

The only downside is several of the *BSDs don't have wayland. Not all the world is linux and sometimes that is a good thing to encourage.

There's nothing about Wayland that ties it to Linux. Wayland compositors tend to require a few features exposed by the graphics drivers (e.g. DRM) but there's nothing stopping the BSDS adding these (iirc FreeBSD already does).

You wouldn't pick BSDs for a desktop anyway, assuming you want a working system and don't want to use Windows/macOS.

Now the concept of a "working system" can be a bit hard to grasp for some people, so let me put it this way: There are vastly more things that normal people do on their computer that work on Linux than on BSDs.

> Our internal metrics within KDE show that over 95% of users of Plasma 6.6 are on Wayland

Wonder how representative of the real end user population this is?

I think most people who even know the difference between x11 and Wayland are much more privacy conscious then those who don’t. 0% of people going out of their way to jump through all the hoops to get plasma working on x11 would ever opt in to such metrics.

Nah, don't think so. When I setup my main dev desktop (a Debian variant) a few months ago it defaulted to X11 and getting Wayland to work on it was a pain in the butt.

That being said, on a different box with an older gen Nvidia card (3070) it defaulted to Wayland and just worked out of the box.

So, bit of a mixed bag. ;)

No headless RDP solution is pretty unforgiveable in 2026 - right now I use Nomachine and indeed it requires X11. Why wouldn't Wayland have a solution for this? It is not a niche usecase. It is like, a headline, completely mainstream use-case.

Blind spot that comes from incompetence and arrogance. See https://lwn.net/Articles/553415/ for example and remember famous words of Daniel Stone that brought the need for remote work to - merely - launch xeyes.

Thus, that particular comment (https://lwn.net/Articles/555124/) was prophetic: "With that sort of attitude, I have no confidence that remote Wayland will ever work properly. Clearly Daniel just has a laptop and does all his work on it, and damn everyone who uses more than one machine for anything."

this take is ridiculous, of course remote wayland will work, there are still some things missing, which are gonna come shortly in KDE atleast.

It seems to me like such a drastic change in the underlying system (removing support of one of two major display platforms) would mandate a major version change.

Complete removal of X11 should be an event to trigger KDE 7.0.

I agree. IMO this is a breaking change. It seems like some (many?) accessibility tools don't work on Wayland, so this breaks users' workflow if they need those tools

KDE 4.0 has already shown that KDE developers have a very different understanding of version numbers compared to users.

I do like how the wayland usage statistic are based on wayland apps crashing more than x11 apps

Crash reports are only mentioned as confirmation of other statistics, and in any case, the vast majority of crashes have nothing to do with the window system used.

Instead of rage baiting you could have just read the blog post to figure out its opt in telemetry, crash reports (most of which won't be x11/Wayland related) is being used as an additional metric to confirm that trend.

Linux users are more likely not to opt-in and actively opt-out of spyware, telemetry, or whatever you want to call it.

The ones that don't are more likely those who leave things on defaults, are involved with the project or a distro, or similar. No, I don't have anything that backs this up. The statistics they're using can never be accurate, by virtue of being free software that ships on privacy concious distros to privacy cincious people. There was a study that backs up this claim, but I'm not google.

OTOH, xfce is doing fine.

Linux are also more likely to contribute bug reports and crash dumps.

Security conscious doesn't mean not getting involved with the community and helping useful projects.

Linux users contribute bug reports to projects that actually care about them and don't leave usability regressions open to decade long bikesheds. KDE is not one of those projects.

Since KDE telemetry is privacy conscious too, I as a privacy conscious linux user see little issue with enabling it.

How do you get that?

They showed the statistics based on their telemetry tools and said they match crash data.

Not that it was 100% from crashes.

Also the fact they can tell which one is in use does not mean that’s the reason it crashed. It could be crashes due to bad network handling or file corruption or something that has nothing to do with the GUI.

And the statistics are only from the latest release, not over all KDE users. They mention this in the text but the disengenuous plot is what people see.

>For transparency, the one caveat in all of the above is that I've deliberately always focused on people using the latest Plasma release. We do still have a sizable chunk of users on X11 still using Plasma 5.27. Including them, the total Wayland adoption rate is about 76%.

Yeah, and considering how KDE developers have been introducing bugs for X11 as their main strategy for Wayland to reach feature parity I expect many X11 users are holding out upgrades as long as possible.

This is a huge blow to accessibility on linux since KDE is such a large marketshare. There is no support for accessibility for the visually (or otherwise) disabled in KDE Plasma's wayland extensions (and none in core wayland at all). It's frankly shocking to me that they would go ahead with this. Even if one doesn't care about the lives of the disabled KDE is now ruled out of workplaces and institutions in the USA because of the Americans with Disabilities Act. The only wayland compositor that supports accessibility it's GNOME's mutter and that's with it's own newly rolled set of protocols that only GNOME's userspace applications support.

I'd love to be proven wrong about KDE's accessibility support. Hopefully they'll adopt GNOME's acccessibility extensions for wayland but that seems less likely than making their own that work with their compositor's design.

> There is no support for accessibility for the visually (or otherwise) disabled in KDE Plasma's wayland extensions (and none in core wayland at all

Can you clarify what you mean by this? In the process of KDE implementing Wayland support I also have seen several issues and blog posts dedicated to accessibility features. In fact, I am fairly sure I saw KDE explicitly funding accessibility development in relation Wayland a while ago.

I am using KDE with Wayland and just had a look in my settings and the Accessibility menu is there and the features in there also appear to be working. Including the screenreader which worked on all windows I had open at the time.

Which makes sense as none of that goes through the display server but rather a D-Bus protocol implemented by Qt and GTK as far as my understanding goes.

There is a bunch of stuff that came with X11 "for free" like access easier screen capture for magnifiers, input injection, etc but as far as my understanding goes KDE (just like GNOME) has been working on DE specific implementations of each.

I am not saying things are perfect right now as far as accessibility goes. I am not someone who depends on these features. I also know that things are in fact not perfect across the board and there is still work to be done. But the claim that there is no support for accessibility seems like a rather large hyperbole to me.

That is good to hear. But the third post down on acidiclight's mastodon page is a link to another user's blog post:

>As a KWin developer and KDE's accessibility engineer... >https://nocoffei.com/?p=451 >This is a problem. We need to solve it. Fast.

And this is a quote from the page intro,

> As the Linux Desktop transitions to a Wayland-only future, I will be locked out of my computer, as the accessibility software I rely on is left behind. The desktop environment I use, KDE Plasma, has announced that in early 2027, X11 support will be removed from the system. That means in about roughly 9 months, I will no longer be welcome on that desktop environment, being forced to cling to an older version or switch to a more niche environment that still supports it.

The problems described therein haven't been fixed. And mclassen's (of gtk) comments on the fedora bug tracker make it clear that even if KDE tries to implement GNOME's new AccessKit it still won't solve the problems. mclassen seems to think the people asking for things like getting and setting cursor position are just sealioning "accessibility maximalists". The core idea of his argument argument is valid, you can't get it working all at once and progress is incremental. But if that's true then don't remove X11 support that works while the waylands are still progressing towards working.

Does anyone know if there is any progress on window shading on Wayland? I miss it like crazy.

Same. Given that no Wayland compositors implement it, or anything like it, and from some of my surface level reading about how compositors work, I get the impression Wayland is particularly ill-suited for this feature. I don't understand enough to understand exactly why, or why a new Wayland "protocol" would be required, though that seemed to be the answer. I hate not having this feature, it makes me feel trapped in an entire desktop paradigm I don't desire to be locked into.

"We can't promise to get everything fixed in time for 6.8, but we can promise to listen and be aware. "

What is with KDE and releasing broken software? What's the rush to release when there are known issues?

qimgv uses libmpv for video playback support for example. I'm guessing that's not what you mean, but I'm struggling to think of how one might "embed" one application inside of another on xorg.

x11 supports foreign window embedding. You can embed window from other application into your own window. That's why lots of mpv/vlc based players/editors don't work probably on wayland. The only way to achieve this on wayland is writing a custom compositor for the foreign window.

I worked at a company that had a powerful legacy software that was meant to be configured once and run full screen.

At some point it needed a custom interface and the ability to reconfigure itself on the fly.

Adding in a GUI was not a reasonable option.

We ended up writing a GUI (in gtk) then using Xembed to embed the other process and communicate via a Unix socket.

What would have been a major rewrite (and likely a port to a different language) ended up being a few a days project and worked beautifully.

It really showed me how powerful X11 really was.

Slight tangent but has anyone moved from AwesomeWM to a Wayland-based tiling WM? Interested to hear what people chose. I tried Sway for a bit and while it's not bad by any means it's a bit too unlike what I'm used to. SomeWM is an attempt at "porting" AwesomeWM to Wayland and looks very promising but not quite there yet (I couldn't get Vicious widgets working and not sure if supporting them is even a goal).

I'm still on AwesomeWM for now because I have no real reason to incur the pain of switching, but still curious to know what path others are taking.

(one of AwesomeWM core dev here)

Vicious is getting quite old. We put tons of effort in AwesomeWM to be perfectly backward compatible all the way back to the 3.5.0 API (ok, 4.0 had documented breaking changes, but still had compat code to minimize the porting work), like bug-compatible level using a **ton of `if` in the code. I really can't blame any effort to implement wayland to nuke that compat code mess when it blocks them. The older Vicious most people use is also using blocking code in the main thread, it it locks the entire WM when its calling a shell command. AwesomeWM had async APIs for that kind of stuff for a decade now. IMHO, using some LLM call to port the widget to use the declarative widget API, which AFAIK SomeWM supports, is probably worth it for performance alone, even if you keep using AwesomeWM.

Yes, when looking into it I realised how dated Vicious is these days. It goes to show how long I've been using AwesomeWM I guess because I think it was the shiny new(ish) thing when I first started using it. It doesn't seem like the functionality I want would be that difficult to replicate without it (famous last words) so I may just do that.

Thanks for all your work on AwesomeWM - whether I keep using it or not it has been a great experience!

> not sure if supporting them is even a goal

Technically, it is a goal, though perhaps an optimistic one.

I won't support vicious widgets in the 2.x releases, but I should definitely add support for it in the release/1.4 branch that follows AwesomeWM master/4.4. Not that I think vicious widgets are the best, but technically if it runs on AwesomeWM, I should support it in 1.4.

I created an issue (https://github.com/trip-zip/somewm/issues/599), even if you decide not to use SomeWM. Thanks for trying it out.

I settled on river¹ after a couple of decades with awesomewm. Tiling and tagging work in a way you'd expect coming from awesomewm, but nothing else does. I made my mind up because having to use workspaces and manual tiling is a far harder sell than implementing the functionality I want on top of a decent base.

If anything it reminds me more of the experience with using awesome v2(before lua); you generate a config file for the base WM, and then build up external tooling to drive it how you see fit. The experience has been quite pleasant, but I do enjoy twiddling.

¹ https://codeberg.org/river/river

Edit: I just checked my dotfiles. Awesome went in on 2008-06-09, and river on 2024-06-30. Happy and largely uneventful two years on river.

I had seen river but for some reason didn't look too much into it. I think it's because at first glance it looks like a protocol that you can build a WM on, rather than a WM itself, but I guess it's probably easy to build your own tooling over it (a lot easier than "building your own WM" in the traditional sense)?

I'll give it a look - thanks!

If you want an out of the box test then playing with river-classic¹ is probably a good place to start. It gives a feel for where you can go, without having to put too much effort in.

For example, it has pluggable layouts where instead of pulling in a lua module(such as awful.layout) in awesome you'll run an external process which handles events. You can even run multiple managers and switch between them with bindings, or write a custom one to scratch that itch. If you're happy with just awful's .suit.tile.right and .suit.max then basically any backend will do.

This is why it feels like a reasonable path off awesomewm to me. I always considered awesomewm to be the WMConstructionKit, and while river changes how you interact there is still a nice route to extensibility. The newer direction even more so than the -classic offshoot.

¹ https://codeberg.org/river/river-classic

I hope Debian 14 will have the last x11 version such that users that need it will be able to use it for another 5 years

The main blocker I have for moving is the poor session management. On X11 for decades I've been able to log out of my KDE session and when I log in again, all my Konsole windows re-open with the tabs open in the same folders, Dolphin opens with all the tabs open to the same locations etc.

I think they recently added support at the KWin level for reopening windows to the right desktops etc but as far as each individual apps, it seems to be up to them individually to get this working again. I would have thought that at least for the KDE apps, they could just have a compatibility layer from the X11 session management to make it work but it doesn't seem there yet.

>it seems to be up to them individually to get this working again

Just like on x11 for the overwhelming majority of applications it's implemented in and handled by the applications framework like GTK, QT, electron, ...

Maybe its better under KDE but on gnome/wayland, VSCode can't even remember its window position and size or even which display it should be on - at least for me. Reminds of the bad old days of windows 3.1. I have a shell script to reset it now.

But I have to use wayland because I've got nvidia and the force composition vsync hack is just too slow to game with reliably.

By the way - David refused to publish the source for the image he showed, aka "nobody uses x11 anymore".

This reminds me of the systemd folks - they also don't allow for discussions yet alone cite anything related to their claims. They just claim. If the earth is flat, they don't need evidence. Their word must be enough.

It is this image:

http://blog.davidedmundson.co.uk/wp-content/uploads/2026/06/...

David claims "internal metrics", but he also does not explain how those metrics were gained, is there bias in how they were gained, which time span and so forth.

I am not saying he is fabricating the graph, though this could be the case too. What I am asking for is to show (ALL of) the data and explain the graph and data. Otherwise this is simple propaganda, with a pre-set goal to cover-my-ass (aka explain why KDE devs try to eradicate all xorg users).

By the way, next step, as you guys may know: systemd-only. Both David and Nate also announced this before. I wonder if there are financial kickbacks.

Good old David - he loves systemd. No wonder he does not like X11.

Oldschool KDE devs were better. Today's generation of David or Nate, are just killing KDE off. But no worries, on their blog they'll continue how everything is great. It is so great that they need a donation-widget to keep on pestering people to donate. So now you can pay for them ruining the legacy here.

I don't really like Systemd neither - but Wayland and Systemd are pretty much opposites of each other. Systemd does (too) many things, many of them badly. Wayland does well what it does, but it (still!) does too little. Wayland is adding features and is pretty close to doing "everything necessary". Systemd keeps accreting worse replacements for existing services.

They are actually both much better than the things they replace, but a bunch of whiner babies can't stand the thought of anything changing and will claw and scream while being dragged into the future.

Systemd-resolvd is a bad DNS resolver and journalctl makes logging needlessly complicated and log files slow to read. Also, socket activation is basically xinetd and we got rid of it because it's a brittle hack, also slower than starting stuff as soon as possible if you actually need it.

I’ll agree with some parts of this as I have some big issues with parts of systemd. But writing service files with systemd is so much better and having a unified interface into logs is really really nice.

Sure, there are a few things it's better at. I don't think it's entirely bad, just that the good things are way outweighed by the bad.

Its similar in that Wayland assumes responsibility for all interactions between programs instead of providing unrestricted interfaces that can be used to implement accessibility, automation and whatever other tools people can think of. It's the systemD way or the highway and it's the wayland way or the highway. But yes the situation is also different in that there is one SystemD but many little incompatible wayland compositors.

Funny, my impression of KDE in the 3 and 4 eras was “Wow, this is shiny and sleek— oh, and it crashed. Nevermind.” Nowadays there is nothing I would recommend more to the average user who just wants something normal that works. It just works. What you’re saying just sounds like a pointlessly personal and ideological attack. Against a piece of software. Why?

I dont know when where these "good old days" but in 2000s KDE was superunstable. It seemed to have all the cool UI tweaks but 30% of them barely worked.

Modern KDE is nothing like that, and i cannot see how this is a bad thing.

More and more Free SW will depend on Systemd (like next gen flatpak). Make something better or adapt.

Trinity Desktop supports X11. If you liked KDE3.5 you might like Trinity.

Good bye KDE. Good bye Red Hat. We're doin our own thang now.

KDE 3.5.x really was peak desktop at the time, especially when all the K* apps were working as intended. As a Windows user discovering Slackware 10.2 back 2005, I was really blown away. KDE 4 just didn't feel the same.

One thing in watching the 30 years of KDE talk is the DE-emphasis on apps. The whole thing got to big so it went from SC4 or whaetver into different strains. Modularized, etc. About then serious desktop apps seemed to have died off too

I guess one cares less about DE's when my DE is a front for a terminal and a VM (my browser).

It's sad to see sidelining of KOffice, Konqueror (of course still exists), Amarok and other great apps.

A desktop environemnt is not just a WM + Panel + Decorations.

KDE3.5x has is own... well everything tied together.

I can't be the only long time Linux use who still has no real idea what X11 or Wayland are. Except that sometimes software won't work properly with one or the other and I need to paste some arcane command to fix it.

It's what puts graphics on the screen. If you are not interested in hacking or developing it, there's not much else to know except X11 is deprecated and Wayland is not finished, leading to this suboptimal situation.

I think it is amazing that Linux has reached such an audience that the knowledge of what windowing or desktop system being used is unknown.

But at the same time it makes me a little sad. Part of the draw of Linux was being able to understand what was under the hood and how to bend it to your will.

I’m hope the community doesn’t lose sight of that in trying to gain new users.

People often talk about the year of Linux or what success is, and in my opinion, Linux had achieved success by 1996.

Trying to pull a casual user from windows or Mac OS is a worthy goal, but that shouldn’t be the end all be all metric.

Yep and Xwayland is an X server that runs under Wayland and provides compatibility for native X11 applications, which don't natively run under Wayland.

I prefer software rendering, I don't use compositor, and I never will.

In software rendering, CPU only updates screen when changes are detected. And the change completes as fast as the computer can. So that's minimal latency + minimal resource consumed.

If you're on a compositor, the 3D accelerator in your computer has to update the screen 60 times every second. It's even worse when you have a higher refresh rate display. And compositors update the buffer as soon as the previous buffer is pushed after the v-sync signal, and then it just waits until the next signal comes in. So there comes the terrible input delay. As a result, it comsumes more power and has higher latency.

So in conclusion, fuck Wayland, and I'm going with xfce without compositor.

My concern is that KRdp still doesn’t feel ready to replace the mature X11 remote desktop options. In VM/headless setups, the X11 stack is ugly but predictable, you can run Xvfb, VNC/Selkies/xrdp & control resolution pretty easily.

KRdp on Plasma/Wayland is still much more fragile. It depends on a logged-in Plasma session, has rough edges around unattended access, session startup, reconnection, display sizing, authentication/cert handling, and general automation. Those are exactly the things cloud desktops and disposable VM images need to be boringly reliable.

I’m not against deprecating X11 long term, but deprecating it before KRdp is a solid replacement leaves server/VM/remote-desktop users in a bad spot, hopefully now the team can focus solely on Wayland, KRdp will receive some much needed love.

Time to switch to Windows! yay! Where all of this stuff just works: HDR, remote desktop, gaming, Picture-in-Picture, ... all the stuff that Wayland devs are too stupid to get done correctly

/s (maybe?)

Eh, IDK. Maybe? After 20 years of using Linux I'm looking on Windows more and more.

Linux Gaming is now better than ever, and ideological Linux dev community torpedoes it hard with Wayland.

I mean who Linux wants to be anyway? An OS for bleeding edge hardware? I think we have Windows for that. Because Wayland doesn't even work correctly on average-aged hardware.

Greybeards have created Linux, and cool new generation will shut it down (on Desktop).

You mean: "Deskop Long + live Linux", because Wayland devs decided that's it's the best way to order the words you want to use

dumb question, with LLMs being so prolific now, why is this sort of a thing.. a thing? Why not us an agent to maintain code people use, but humans don't have time to keep up with? or at least, are agents being used in FOSS software widely for such ends, at least to reduce the burden and cheapen the cost of delivering quality FOSS experience?

It's so funny reading about how the problem with Wayland is that you have many, often incomplete, implementations while being old enough to remember the time when X11 was actually popular (and thus had many, often incomplete, implementations).