You can argue that the lack of standardization leads to confusion, but why should the upstream decide the way key system features are implemented?
Philosophically, I agree that Wayland's comparative freedom allows for greater flexibility and more discretion on the compositor developer to implement whatever they want. That's honestly one of the reasons why I respect Hyprland despite vastly preferring Openbox for ricing purposes (What? No! I didn't spend half my high school years learning Openbox's obscure XML syntax just to get upstaged by some sweaty faggot running i3, whatever do you mean?)
The biggest issue I have with the lack of standardisation, insofar as the compositor specification is concerned, has to do with downstream application developers targeting Linux as a platform. On X, everything's already been settled for the better part of several decades. On Wayland, the technology is novel and how you render display and package your binary will ultimately reflect the assumptions you make. GTK is the predominant standard bearer for Linux GUIs, but Qt is cross-platform in ways that GTK can only dream of. Standalone WMs and novel desktop environments
need to make pertinent choices in how they handle their compositing.
Is this about the keylogger again? I have never understood the argument against app isolation in Wayland. It just seems like a blanket positive in comparison to X's way of doing things where everything can see everything else at every time. It sounds disturbing on paper and I legit cannot see a reason for why you'd want it to be that way. X assumes that you trust everything on your system hence the wack "treating us as enemies on our workstations" comment people love to cite. Wayland assumes an untrustworthy system by default, which to me at least, is the saner way to approach it. Security by default, right?
Hot take: I think that Canonical's Mir was honestly the correct approach insofar as novel display protocols were concerned. Wayland assumes an untrustworthy system by default, and preemptively destroys tons of legitimately useful functionality in the process (re: global hotkeys, primary monitor, VNC, etc). Mir, conversely, took the Wayland assumptions and modified them to better accommodate desktop and workstation users. Unfortunately, Mir itself wasn't good software. Yet the
idea behind it was definitely valuable. I can't argue the feasibility over the long term, but I feel like Wayland should've had
some level of flexibility the way other Red Hat-sponsored technologies like SELinux and Firewalld do. Fedora itself already makes broad concessions with Firewalld to open up more ports by default, whereas SELinux policy
technically needs to be modified by the user before it takes effect. If Wayland and SELinux gave the end user broader latitude on any given Fedora system to decide their security model, or even dropped the threat model down to a similar wavelength as what they have on Firewalld, that would honestly be a welcome change.
That's another thing, X is designed by default to be a networked system where everything has access to everything and runs as a client process fo the X server. Just as it is good for you or anyone that wants to essentially just client-server and use their remote device as a thin client for their static one, it is dogshit for ye olde one computer setup because you aren't remoting into anything
I would like to chime in and say that X is far more amenable than Wayland is for my specific situation. I run an Ubuntu home server, I have a minimal graphical environment to do some basic troubleshooting that I don't wanna do the whole CLI shtick for. VNC is invaluable to me because my home server doesn't have any monitor leads. Using a Wayland-first distro (i.e. Fedora Workstation or Fedora Plasma), VNC is a non-starter because Wayland removes that option entirely. I need to rely on RDP, which
technically gets the job done, but not in a manner that I find satisfying, let alone ergonomic to use semi-regularly. On Fedora Cinnamon, which is Xorg-forward, VNC is effortless and honestly
much more comfortable to use. I can't give a technical explanation beyond RDP feeling jank, laggy, and like I'm fighting against my computer vs. VNC actually feeling buttery smooth because it has access to framebuffer data (I think that's what it is, anyway).