Linux

67456 readers

177 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago

MODERATORS

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

Why isn't there a compositor agnostic Wayland API for window focusing? (lemmy.ml)

submitted 5 days ago by mawkler@lemmy.ml to c/linux@lemmy.ml

46 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] ranzispa@mander.xyz -1 points 5 days ago (1 children)

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.

[–] JTskulk@lemmy.world 8 points 5 days ago (1 children)

KDE is dropping support for X11 next year: https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/

[–] ranzispa@mander.xyz 7 points 5 days ago (2 children)

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?

[–] PushButton@lemmy.world -1 points 3 days ago (1 children)

Your grave is wide and deep enough, you can stop replying and jump in.

[–] ranzispa@mander.xyz 1 points 3 days ago

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.

[–] JTskulk@lemmy.world 0 points 4 days ago (1 children)

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.

[–] eldavi@lemmy.ml 2 points 4 days ago

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