this post was submitted on 11 Feb 2025
537 points (96.2% liked)
linuxmemes
22678 readers
540 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not sure what you mean with "all of wayland", here. The protocol is ludicrously small and minimal. It's a way for programs to say "I have a graphics buffer, please display it and also give me some input like mouse motions plz". Everything else is extensions because there's devices (e.g. in automotive) that need only that, and nothing more, no windowing no nothing. You certainly don't need global hotkey handling if all you ever run is one full-screen client.
Whether the compositor wants to implement windowing logic (say, tiling vs. floating, what happens when you right-click a titlebar) itself or outsource that to another process is not wayland's concern.
KDE didn't go that way because kwin was already an integrated compositor and window manager when it only ran on X, the smaller projects do seem to tend into that direction but they haven't agreed on a common standard, yet.
Global hotkey handling, copy and paste, screenshots, etc are part of the protocol but need to be implemented by every compositor. X is better for this; the server handles all of this and delegates window management to the WM.
You're not making an apples-to-apples comparison, the x protocol does not do ANY of those things, the x server does, you're comparing an implementation of a protocol to a protocol... and then saying the protocol should magically just do it, even though that isn't the purpose of a protocol in the first place. The only difference in this case is that there's just one serious implementation of xorg because it sucks to work with so much that nobody else will do it, this is actually just a knock AGAINST x.org that you view as a win because standardization, in practice, it doesn't matter at all.
the more correct comparison would be x.org to wlroots, which does most of them (global shortcuts is being worked on still) or smithay.
Maybe someday in the future everything will standardize around wlroots or smithay, but the fact that they haven't is because it's so relatively easy to make a wayland compositor from scratch that the need for standardization is tiny. Gnome and KDE wrote their implementations BEFORE smithay and wlroots existed, and hyprland came along and did it basically on their own from scratch... a feat that could have NEVER been accomplished with x.org, as evidenced by the fact that nobody has rewritten it in rust or whatever.
Essentially you're saying they "have" to implement it themselves, when in reality, they GET TO implement it themselves if they want to, because the design is so much better.
If they don't WANT to, smithay and wlroots are there for you to use. It was a deliberate choice by those teams to make and maintain their own thing, if somebody wanted to do that with x.org, there's literally no reason they couldn't, the x.org server doesn't prevent this in any way, and even if it did, would that really be a strength? Your argument just fundamentally doesn't make sense if you actually understand these things.
I think you should double-check what I linked to: To the xdg desktop protocols, that's a dbus thing, it's not a wayland extension much less the core wayland protocol. It's the same protocol flatpack apps use to do stuff, figures that APIs that are useful if you're in a sandbox are useful in general.
X does not handle global hotkeys. It gives everyone full access to everything and then expects them to not fight for control, which took decades to actually happen, before that the desktop would often break down as clients were fighting. Any client can warp the pointer, capture all keys, watch how you enter a password in another window, say it's the one which should be on top of all the others, it's a nightmare.
Judging by the types of misunderstanding you have I must assume that you've never written a single line of X or wayland related code. Know, therefore, that you are completely unqualified to hold the opinion you have, much less hold it strongly.