I've been daily driving a work laptop with Wayland for over a month now.
the good: it works! and KDE works well with it, plugging and unplugging HDMI cables always does the right thing, scaling with different monitors looks okay too.
the bad: every time I need to learn how to do something I knew how to do on X11 (e.g. custom keymaps or xrandr voodoo), I need to learn a method *specific to KDE* because there's no DE-agnostic tooling.
gamedev @hisham_hm If I'm not wrong, DE-agostic things lives on freedesktop tools, like xdg.
The one I remember is xdg portals, but seems it's a flatpak thing actually.
@hisham_hm well blame that on endless bikeshedding over at freedesktop gitlab.
I would like to call @BrodieOnLinux to the witness stand.
PS: In the interest of transparency, Brodie is a wayland shill.
@hisham_hm That's very much my experience with Wayland. It does what it promises, and makes me appreciate all the X tooling that's missing
@tfb It's almost as if everything that was bad with X, it does better, and everything that was good with X, it does worse.
(Which is somewhat understandable, because when building a competitor one tends to focus their energy on the incumbent's weak spots.)
@hisham_hm i started using Wayland (kde) experimentally, and so far its working, including HDR high refresh rate display with scaling. Which is nice.
Have not tried remote desktop (not rdp, something like vnc) that didn't work last time because no keyboard.
@hisham_hm the ugly: the lack of DE-agnostic tooling is mirrored in the lack of DE-agnostic API, which means that wayland makes interesting Linux desktop integration exponentially more expensive for independent app developers, even exponentially more expensive than X11 already was as compared to other OSes. It is truly miserable.