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?
if i’m fine with how it is, why would i help change it?
So people trying to use it could more easily do so.
Because you believe in the principles behind it and want to bring them in harmony with the ops problem.
As an action in support of the open source principles you espouse, improving the commons for no other reason than your empathy and love for the human spirit!
99% of people who wants to use it does. wayland literally just works.
What are you trying to say here?
It clearly has a serious problem that the op is experiencing. Why not help the op instead of dismissing their concerns? It really seems like you’re trolling or at least engaging in bad faith here…
why don’t you? you seem bothered by it and maybe op stumbled upon something worth looking into.