I enabled wayland recently and there’s been a lot of annoyances to the point that I wonder why I bother considering X11 works without these issues. For example:<p>* Chrome needs a bunch of extra flags to launch in Wayland mode<p>* Firefox needs extra flags to launch in Wayland mode<p>* Xwayland is just broken on Nvidia with both sides refusing to compromise (implicit vs explicit synchronization - Nvidia refuses to add implicit and Xwayland refuses to take Nvidia’s patch to do explicit). What this means is that you get tearing, flickering and all sorts of terrible graphical artifacts<p>* Chrome only just fixed HW acceleration for Nvidia (latest m120 beta)<p>* enabling vulkan causes Chrome to fail to render (although this may just me needing to try reinstalling Nvidia drivers)<p>* I thought it was an acceleration thing, but even with HW acceleration fixed Chrome has a bug where the mouse pointer leaves behind white speckling when mousing over on a dark background. VSCode doesn’t have this issue.<p>None of these issues appear in X and this is from someone who thought Wayland is the right way to go (eg you didn’t see this kind of story on Mac when they switched to HW accelerated compositing).
It's been kind of buried, but KDE has the first steps of tiling mode built into it now, in addition to the default screen edge tiling (on KDE 5.27.8 on up). Meta + T to enable tile editor. Shift + window drag to move a window into a tile.<p>Hopefully a lot more coming, including different layouts per virtual desktop & full keyboard nav for the tiles. But it's a decent start.
For more background in general I recommend the blog of one of the main developers, for this wayland news specifically this article: <a href="https://pointieststick.com/2023/11/10/this-week-in-kde-wayland-by-default-de-framed-breeze-hdr-games-rectangle-screen-recording/" rel="nofollow noreferrer">https://pointieststick.com/2023/11/10/this-week-in-kde-wayla...</a><p>This article from september goes into wayland (and KDE) much deeper and is worth a read: <a href="https://pointieststick.com/2023/09/17/so-lets-talk-about-this-wayland-thing/" rel="nofollow noreferrer">https://pointieststick.com/2023/09/17/so-lets-talk-about-thi...</a>
> - Plasma's start time is up to a few seconds faster.<p>On the one hand, this is impressive. On the other, this is a vague indictment of modern software. Plasma logs you in, draws a background and the taskbar thing across the screen. There shouldn't be seconds involved in that to shave.<p>This must be a recurring feature, every few years someone goes through and fixes up load times.
Wayland has a few glitches, but in general it's good to use.<p>For example, it doesn't have an API to get current cursor position (which breaks keepassxc's browser popup, goldendict's query popup), an API (which most compositor implements) to get current window state, which makes me unable to find an alternative of autokey (kwin script can do this, though, but it lacks the ability to execute arbitary commands..).<p>On the other hand, I don't see a killing feature that drives people switch to wayland.. (HDR can be one, but I don't use it) I mean, yeah X11 is old and unmaintained, but it WORKS.
I really like KDE. I feel like it's what the windows DE wants to be when it grows up. Everything is configurable and it's usually fairly obvious how to do so.<p>Coming from a long time 'minimalist' linux users, my biggest issue with it is that there's no ~/.config/kde that you can just copy between machines and get set up the way you like it. It's spread out all over the show.
Wayland doesn't fractionally scale chrome, discord, vscode, spotify, beeper, and other appimage and non-native applications. So even if KDE enables it by default, most users will have to switch back to X.
I've been using Wayland KDE on my gaming machine recently, it somehow made my cursor movement stutter. Switching to KDE X11 or Gnome Wayland solved the issue.<p>I hope they address this kind of thing prior to making it a default.
Anyone tried KRDP yet? I am very interested to know if they managed to do a good job.<p>One of the main reasons I went back to Gnome was the out of box support for RDP.
This is great. Running Wayland has only been getting better.<p>Hoping this transition to default will get the attention of developers at Zoom, and they can get screensharing to work in their native app without resorting to browser mode or some virtual camera hack. My biggest gripe for sure.
I think I'll wait for another cycle or two before moving to Wayland. Seems like there's a long tail of small issues that need polishing. The zoom screenshare one scared me off a long time ago.
last I checked nvidia on wayland was all kinds of broken, especially with multiple displays, can't rotate a display either. So I assume that has all been fixed then? (j/k)
KDE is pretty feature-rich, but it is just ugly. Look at the poor use of spacing/margins, the ugly black & white icons, the ugly font, the square edges, and just the overall look & feel. It needs a major face-lift. I dislike the attempts to dumb down GNOME but KDE being ugly makes it really hard to switch to.