Generally, core Wayland is very minimal. It's meant to have only the pieces that are essential for every Wayland implementation, not just desktop window managers. Therefore you have xdg-shell extension which is meant for desktop and its windows, you have ivi-shell which is meant for automotive applications and you can have your own extension if your use case is different enough to need it. Thanks to that, KDE and GNOME don't have to implement any IVI stuff and cars don't have to know how to minimize or maximize a window, which, as a concept, might not even really exist there.
There's a widely supported protocol extension called xdg-shell which is used for desktop application windows:
https://github.com/wayland-project/wayland-protocols/blob/ma...
It sounds like, for wayland to actually be usable, you need to define protocol extensions that bring it to feature parity with X11.
At that point, why not just deprecate and replace the two(?) things that are problematic with X11: the keyboard logging protocol, and lack of access control on screenshots?
Surely, that is easier than reimplementing the entire graphics stack, all window managers, and all applications.
Because X11 is a huge dumpster fire that no one wants to maintain. How would you feel about maintaining a 30 year old legacy piece of software which has changed hands 5-6 times since its inception? Wayland is truly a better design and everyone is in favor of leaving that codebase behind.
?
Could you explain that further? I haven't followed wayland much?