Yep you read that right, we’ve decided to throw the lever and go Wayland by default! The three remaining showstoppers are in the process of being fixed and we expect them to be done soon–certainly before the final release of Plasma 6. So we wanted to make the change early to gather as much feedback as possible.
Excellent news. Of course, distributions will still be able to opt for the unmaintained, deprecated X.org if they want to, but most distributions will opt for Wayland, as all the major ones have been doing for a while now.
I don’t know about the rest of you, but there is pretty much only a single use case preventing Wayland from being my default display server on my primary desktop. I’ve been using Synergy / Barrier / Input Leap (thank you forking) for a very long time. Having a single keyboard/mouse at my desk where I have a lot of monitors spread across 3 systems, it’s a God-send. But implementing Wayland support has been a long process for those supporting those projects, and only recently has there been initial support showing up.
I’ll probably try to hack in Plasma support on a local fork, but this isn’t an easy codebase to work on.
jasutton,
I also have similar use cases with remote utilities that to date haven’t worked with KDE on wayland. I’ll keep trying to see if things are fixed but we might just have to get use to wayland devs dictating what we can and cannot do I suppose.
Throwing my hat into the ring too. With Xorg I can use remote apps across Linux, BSD, macOS, and Windows seamlessly. With Wayland I can’t. It’s that simple.