Wayland? Does it have colors, window position memory or hotkeys yet? Or are they still in the "we only sell an idea, you do all the work" vaporware phase?
Wayland seems to have problems showing colors properly. I was trying to fix this issue myself a couple weeks ago.
Colors in Xorg and Windows(gross) show properly, Wayland always looks dull and muted in comparison. Switching color profiles didn't change anything.
But hey, maybe there's a fix I haven't tried yet that works... I sure would hate to be proven wrong! No seriously, if someone has a fix for the dull colors I would likely start using Wayland again.
between sway, hyprland, and kde I've never seen this color issue you're describing, on three different laptop displays and one external monitor. maybe there's something else going on?
I'm running Gnome on Nobara, switching between Wayland and Xorg there's a noticable difference in the vibrancy of the colors. Xorg and Windows both look fine, it's specifically under Wayland that everything dulls out. Multiple displays, displayport/hdmi makes no difference.
That said, this problem doesn't affect everyone. Makes it much harder to troubleshoot. Color profiles don't alter anything, I don't have an HDR display and most of the forums I've found regarding this are having issues with HDR.
I have no idea at this point and limited free time to work on it when Xorg has been working fine. That said, I figured I'd throw it out there in a thread where people are praising Wayland to see if someone knows something I've missed. XD
org.freedesktop.portal.GlobalShortcuts allows apps to request a global shortcut binding from the compositor. They can't just log all your keystrokes globally because that'd be a keylogger. Also there'd be no way to resolve conflicts between shortcuts.
If your app doesn't support that then blame the app, the interface has been out for a while, and compositors have supported it for a while.
kinda sad that users can't (afaik) enable global keyligging for all applications. I totally understand why it's a bad idea, but it's just so much simpler to work with.
Security aside if there's no central management you can have multiple apps listening for the same keybinding, I wouldn't call that "simpler to work with". It may be easy in the short term, but the dark side of the force always is.
What is missing that makes it a deal breaker? It really seems odd to always see comments effectively saying "we should have stayed with X.Org". The nice thing about Wayland is that it's maintained, so new features are being added over time.
You're aware you just called the x.org developers Elon, do you?
x.org is just as much a freedesktop project as wayland is or dbus. Or, before they spun off, flatpak. Wayland grew out of the x.org devs deciding that the thing has become literally unmaintainable. The recent pain is caused by downstream devs (including kde, gnome etc) noticing quite late that the x.org people were actually being serious, if they had provided input earlier then the gazillion of protocol extensions that people are whining about now (such as global hotkeys) could've been finalised literally ten years ago.
x.org still gets a couple of patches -- for xwayland. At some point they're going to rip out the whole graphics driver stack and replace it with a wayland compositor, that compositor plus xwayland will be the X server. You're free to build a PC with a good ole S3 Trio but don't expect future x.org releases to support it.