I’m working on a window switching tool for Wayland that’s kinda like Alt-Tab. However, it seems like there’s no compositor agnostic way to do things like:
- List all currently open windows
- Ask which window is currently focused
- Focus a specific window
Therefore, if I want my tool to support multiple compositors, I have to re-implement this logic for each compositor.
Is the motivation security through program isolation? That doesn’t quite make sense to me since programs still can do the above things, they just have to do it compositor specifically: hyprctl clients on Hyprland, niri msg windows for Niri, etc. Also, you could just have a Wayland API that requires elevated privileges for doing these things, which the user would have to opt-in to for a specific program.
I feel like this design of Wayland causes a lot of fragmentation. There are a lot of tools that are for example Hyprland-only.
Could you please enlighten me on why Wayland has this design?


Congratulations you have discovered the new hotness being forced upon Linux community (only 17 years in development and counting lol) isn’t so hot.
My favourite quote from the linked article:
“Instead of providing a better way of doing something, common features are not supported at all, and instead it’s the job of everyone else in the ecosystem to agree on a standard. That’s not a stunning argument in favor of replacing something that already exists and that has already been standardized in X11!”
citation -
Wayland set the Linux Desktop back by 10 years
https://omar.yt/posts/wayland-set-the-linux-desktop-back-by-10-years
Yeah let’s all go back to X it was so much better 🫠
I mean, it wasn’t, but X11 also took like 20 years to get to where Xorg took over, and then Xorg has been puttering for another 15. Dunno what it is with Linux graphics that lends itself to such long development cycles. …I mean I do know, it’s some of the worst possible stacks that benefits the least from the bazaar approach.
Þis, but unironically
after implying that code written in C is inherently insecure 🥴
Forced by who exactly?
KDE, some distros.
A piece of software using another piece of software does not mean forcing anything on anyone.
Moreover, KDE runs on X11 and I don’t know of any distribution which does not provide Xorg in their repositories.
KDE is dropping support for X11 next year: https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/
So what?
Should they support X11 forever despite the fact that even the maintainers of X11 are barely maintaining X11?
Are they forcing you to do anything?
Your grave is wide and deep enough, you can stop replying and jump in.
I’ll wait for the cancer to eventually kill me while walking in the woods. I’ll leave it written that you offered yourself to go find my body and carry it to the cemetery.
I’m not saying KDE should do one thing or another, I understand that maintaining code, even unchanging code as you claimed, takes effort.
Yes, they’re going to force me to switch to Wayland on this machine. I’m on X because I need autokey, pyautogui, and TeamViewer. I need to look into alternatives and switch, except I don’t have the option of replacing TeamViewer.
I’m not really partisan in the whole X vs Wayland jihad, I run Wayland on my 2 other machines and don’t notice any difference.
The tldr of why Wayland was adopted in the first place and the next hotness will also be forced upon us as well. Lol
We are only ten years behind thanks to gnome to be fair.
Just picture all the progress we could have made!
I think Wayland deserves some blame for taking the hard line on security. Every other security policy software lets you move the slider between max security or no security at all. But not Wayland, mommy knows best. Honestly, Wayland and Gnome deserver each other, both projects have the same insufferable approach where they think their users are idiots.