"You can take your seat capability pointer and wl registry listener and shove it up your a*." Well it's not my API and this is also incredibly rude, please don

"You can take your seat capability pointer and wl registry listener and shove it up your a*." Well it's not my API and this is also incredibly rude, please don't say these things to people online. You should not be using the low level Wayland API unless you're developing a toolkit, you will always have a rough experience with that. The only reason to use that is if you want to write all that boilerplate. I suggest developing using the GNOME and KDE libraries that they have for this, which handle the boilerplate for you. Seriously, the Wayland API is not meant for normal user-facing applications. The number of projects that actually need to worry about it is pretty small and it's limited to pretty much just compositors and toolkits and a few other glue libraries. Don't try to use it like it's the X11 API because they're not the same and you'll just run into trouble if you do that. "They are both part of the reason the Linux Desktop never took off." I agree with this to an extent but X11 is also part of that same problem. KDE and GNOME were originally X11 desktops (and still are). And if you don't care about this I'm very confused as to what you're doing with a Linux desktop, that seems like a recipe for pain.