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?
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.