EDIT: I just realized in the linked gist they’re basically complaining Wayland doesn’t have “builtin” support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Screen recording works, I think it’s only existing X software that doesn’t. In my experience there’s still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don’t know if there’s a way to capture an application and its audio automatically.
Global hotkeys refer to hotkeys that can be activated while the application isn’t focused. Wayland has global hotkeys, but some people don’t like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can’t display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.
I also don’t know what they mean by clipboard management, but I do know there’s some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn’t work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don’t know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.
Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren’t yet incorporated into Gnome. But more generally, Wayland deliberately didn’t implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don’t manage it. That’s due to the choices that went into Wayland.
AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that’s a design choice that also means WMs don’t have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.
To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.
That’s simply not a failure of Wayland, it’s a tradeoff they chose, and it seems dishonest when people say things “don’t work on Wayland” because the responsibility is deliberately moved to a portal or something.
It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they’ve forced them to either catch up or die. I don’t know that that’s indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I’d switch back to my i3 setup.
I think the “die” part is a bit of an overexaggeration, it’s true that they need to implement protocols if they want the features those protocols exist to provide, but the X way seems to have caused more problems in the long run. Niche projects will attract people who want that niche, hopefully despite missing features, and some people who can help implement those features.
It’s worth noting that DEs can do things like use XDG portal implementations from another DE, I think it might’ve been Niri that does that.
if x11 had HDR I’d switch back to my i3 setup.
Then I can wish you that you get a worthy compositor/DE/whatever to replace i3 on Wayland. Either that or i3 somehow getting a Wayland implementation. I’m lucky in that I was comfortable on plasma with X, so switching to Wayland was mostly painless, though there were significantly more issues back then.
It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to.
I’m not going to defend the state of X and the problems it’s caused because it’s a fugly old project, just when you look at something like pulse -> pipe wire, there wasn’t a big paradigm shift with it. It did the same job and better (to my knowledge!).
I didn’t know that DEs could use others portal implementations, that seems neat?
Yeah it’s the specifics of that that’s the issue for me though. I tried hyprland and many things are really cool about it but lots of things just break, and maintaining separate configs for what feels like core features was annoying. Then you get things like HDR performing differently between it and plasma, something that I’d hoped Wayland would just own. I’ll probably try niri and sway at some point, they both look cool
@kuberoot@FishFace
Yes, but this makes wayland good for everyrhing except normal desktop. It’s pretty good for VR/spatial desktops (where we do not want to deal with 2d coordinates), for some embedded setups where we only need to manage output to multiple displays or draw some overlays. But on normal desktop we need draw UI (wayland cannot do drawing at all!), position windows (limited), capture screen (actually done outside of wayland???) warp mouse (broken?), inject events for automation (yes, ei exist, but looks like very optional…), set screen resolution and layout (actually made different in every implementation?), manage clipboard (still depends on compositor?)
So, wayland actually does almost nothing for desktop :(
Sure, Wayland “actually does nothing”, if you only and specifically mean things that are built into Wayland and only Wayland, the core project, itself.
Meanwhile, as an actual user of a normal desktop on Wayland I can capture the screen, mouse warping works, I have an autoclicker, my screens have resolution, layout and scaling set, my clipboard and clipboard history work (with individual exceotions, accessible from a command line tool too). Hell, I even have HDR on because I found out it just works nowadays, even though my display is probably ass for HDR, but SDR content seems to look no different with it enabled.
Window positioning is something that’s not finished, because the developers are trying to figure out a good way to do it and are taking a long time.
Not sure what you mean by “drawing”, is it some pedantic bullshit again about how Wayland itself doesn’t dictate how you render stuff? Because I certainly have all kinds of GUIs running on my computer.
So if you want a system that is hardcoded to only support things that are common nowadays and that will start breaking down in the next 10 years as things change and the code becomes impossible to maintain, maybe go contribute to XLibre. I will meanwhile patiently enjoy Wayland getting better, even if it might take years, because I have hope that this approach will work.
Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.
Not OP, but wanted to address some questions:
EDIT: I just realized in the linked gist they’re basically complaining Wayland doesn’t have “builtin” support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Screen recording works, I think it’s only existing X software that doesn’t. In my experience there’s still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don’t know if there’s a way to capture an application and its audio automatically.
Global hotkeys refer to hotkeys that can be activated while the application isn’t focused. Wayland has global hotkeys, but some people don’t like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can’t display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.
I also don’t know what they mean by clipboard management, but I do know there’s some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn’t work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don’t know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.
Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren’t yet incorporated into Gnome. But more generally, Wayland deliberately didn’t implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don’t manage it. That’s due to the choices that went into Wayland.
AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that’s a design choice that also means WMs don’t have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.
To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.
That’s simply not a failure of Wayland, it’s a tradeoff they chose, and it seems dishonest when people say things “don’t work on Wayland” because the responsibility is deliberately moved to a portal or something.
It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they’ve forced them to either catch up or die. I don’t know that that’s indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I’d switch back to my i3 setup.
I think the “die” part is a bit of an overexaggeration, it’s true that they need to implement protocols if they want the features those protocols exist to provide, but the X way seems to have caused more problems in the long run. Niche projects will attract people who want that niche, hopefully despite missing features, and some people who can help implement those features.
It’s worth noting that DEs can do things like use XDG portal implementations from another DE, I think it might’ve been Niri that does that.
Then I can wish you that you get a worthy compositor/DE/whatever to replace i3 on Wayland. Either that or i3 somehow getting a Wayland implementation. I’m lucky in that I was comfortable on plasma with X, so switching to Wayland was mostly painless, though there were significantly more issues back then.
It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to. I’m not going to defend the state of X and the problems it’s caused because it’s a fugly old project, just when you look at something like pulse -> pipe wire, there wasn’t a big paradigm shift with it. It did the same job and better (to my knowledge!).
I didn’t know that DEs could use others portal implementations, that seems neat?
Yeah it’s the specifics of that that’s the issue for me though. I tried hyprland and many things are really cool about it but lots of things just break, and maintaining separate configs for what feels like core features was annoying. Then you get things like HDR performing differently between it and plasma, something that I’d hoped Wayland would just own. I’ll probably try niri and sway at some point, they both look cool
@kuberoot @FishFace
Yes, but this makes wayland good for everyrhing except normal desktop. It’s pretty good for VR/spatial desktops (where we do not want to deal with 2d coordinates), for some embedded setups where we only need to manage output to multiple displays or draw some overlays. But on normal desktop we need draw UI (wayland cannot do drawing at all!), position windows (limited), capture screen (actually done outside of wayland???) warp mouse (broken?), inject events for automation (yes, ei exist, but looks like very optional…), set screen resolution and layout (actually made different in every implementation?), manage clipboard (still depends on compositor?)
So, wayland actually does almost nothing for desktop :(
Sure, Wayland “actually does nothing”, if you only and specifically mean things that are built into Wayland and only Wayland, the core project, itself.
Meanwhile, as an actual user of a normal desktop on Wayland I can capture the screen, mouse warping works, I have an autoclicker, my screens have resolution, layout and scaling set, my clipboard and clipboard history work (with individual exceotions, accessible from a command line tool too). Hell, I even have HDR on because I found out it just works nowadays, even though my display is probably ass for HDR, but SDR content seems to look no different with it enabled.
Window positioning is something that’s not finished, because the developers are trying to figure out a good way to do it and are taking a long time.
Not sure what you mean by “drawing”, is it some pedantic bullshit again about how Wayland itself doesn’t dictate how you render stuff? Because I certainly have all kinds of GUIs running on my computer.
So if you want a system that is hardcoded to only support things that are common nowadays and that will start breaking down in the next 10 years as things change and the code becomes impossible to maintain, maybe go contribute to XLibre. I will meanwhile patiently enjoy Wayland getting better, even if it might take years, because I have hope that this approach will work.
Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.