Those are all good reasons. XFCE aims to support Wayland with the next release, so if they choose to use an established compositor it shouldn’t be too buggy.

With XFCE porting their apps over the setup shouldn’t change much, unless you’re using Xorg specific tools.

Over the last few years most features I’d expect from a windowing system were added to Wayland, so I expect the drama to cool down. (I don’t even know what’s still missing (except accessibility), with VRR, tearing, DRM leasing (VR), and global hotkeys being done. It’s just apps like Discord that have to cave in under the pressure to fix their apps.)

Once everything works, there’s no point talking about it.

@Furycd001@fosstodon.org

I wonder how long it’ll be possible to build Gnome with Xorg support. If I had to guess I’d say there won’t be any support within the next 3 years, because keeping future Gnome working with Xorg is work nobody wants to put in.

That said, Xwayland will likely keep being around for the foreseeable future.

Out of curiosity, do you use Xorg and if yes, what’s keeping you from using Wayland?

I’d say flatpak isn’t the future because it’s already here and seems to be universally accepted as the cross-distro package manager.

I do like how the Nix package manager handles dependencies, but it’s not suitable for app developers packaging their own apps because of its complexity.

If a better flatpak comes around I’d use it too, but at least for graphical apps I don’t know what it’d have to do to be better. In my opinion, flatpak is a prime example of good enough, but not perfect and I’d be surprised if there was a different tool with the same momentum in 15 years (except snap, but they seem too Ubuntu specific).