I started working on Flyaway with the intention of becoming familiar with Wayland, its protocols and extensions, and the wlroots library. Instead, I ended up genuinely liking all three.
I generally like what Wayland is doing. The only downside is that with Wayland just being a protocol, the implementation is now dependent on your desktop environment rather than everything sharing the same X server. KDE’s Wayland implementation supports variable refresh rate but GNOMEs does not, and this means gaming is better in KDE than GNOME whereas with X it is pretty much the same experience for gaming on both. I prefer GNOME’s user interface, but giving up VRR is not worth sticking with GNOME.
Yeah, I’m also concerned with how it may affect apps down the line. For example, an app relying on desktop specific features that are present in some desktops wayland implementations but not others.
I generally like what Wayland is doing. The only downside is that with Wayland just being a protocol, the implementation is now dependent on your desktop environment rather than everything sharing the same X server. KDE’s Wayland implementation supports variable refresh rate but GNOMEs does not, and this means gaming is better in KDE than GNOME whereas with X it is pretty much the same experience for gaming on both. I prefer GNOME’s user interface, but giving up VRR is not worth sticking with GNOME.
Yeah, I’m also concerned with how it may affect apps down the line. For example, an app relying on desktop specific features that are present in some desktops wayland implementations but not others.