Nothing about being assholes, just a bureaucratic design.
Also, wayland builds only on the pure kernel abstractions for video drivers (DRM+KMS), which is (was) not supported by nvidia (which instead patched your xorg binary with their proprietary code). No sane person wanted to support nvidia’s way for a completely different render path, so it wasn’t initially supported, until nvidia came to their senses and also implemented the necessary linux subsystems in some of their drivers. So pretty much the same old “Linus middle finger” story, nothing specific with wayland.
That said, having a bare-bones protocol that fails to include standard features, forcing each implementation to meet users' needs differently, is somewhat disappointing. Anything that reduces functionality for the sake of ease of maintainability is going to be unpopular with end users who have everything to lose and nothing much to gain directly.
https://gitlab.freedesktop.org/wayland/wayland/-/issues/32
Attentive designers would have standardized this in the incredibly obvious way of allowing the user to white list specific apps, logically at install time and screenshot apps would then implement a singular standard that works in version 0.1. Instead we force users to confront and understand the difference between x11 xwayland and wayland in order to figure out why their screenshot app doesn't work or doesn't work well.
This doesn't enhance the case for "regular" people to use Linux.
I don't believe I, and the many users who share my preference, deserve insults for that.
