So your best bet is to commit now to switching, entirely, to Wayland. The aim is to get everyone off of X altogether as quickly as possible, and then stop shipping X (including XWayland) altogether.
So your best bet is to commit now to switching, entirely, to Wayland. The aim is to get everyone off of X altogether as quickly as possible, and then stop shipping X (including XWayland) altogether.
Well doesn't that mean XWayland will be easy to maintain since it has no hardware dependencies? X can completely stagnate so long as the Wayland back-end is kept up to date with any changes there - and no, people don't want to be changing Wayland protocols because every compositor would have to be updated. I think XWayland will be around for a while yet, but I'd rather have things run native Wayland.
Ah, it is the "32bit isn't needed anymore" all over again. Yeah, this will happen around the same time you wont need to ship 32bit support on Linux :-)
This is where we're at with Wayland and X.
Besides, even though i am not interested in taking over Xorg, if something breaks on it i'm more likely to look into fixing it than switching my environment to Wayland.
Wayland may turn out to be a flash in the pan. Those applications aren't going away. I have many open source and proprietary applications which I fully intend to carry on using. They don't, and won't, support Wayland.
Unless you're using a modern toolkit which will be modified to support Wayland, you're not going to be using Wayland in a hurry. Because you'll be tied into the X11 world.