Wayland is the poster child for a rewrite that tries to be 'simple' and in doing so over-complicates things by under specification. Other commenters have mentioned that usability extension issues but I wanted to discuss my experience as someone who maintains their own wayland client (for drawterm: https://github.com/9front/drawterm ). There are plenty of technical differences between how KDE, Gnome, and Wlroots that…
A "simple" solution to a necessary complex problem is just kicking the can down the road, and essentially asking everyone to invent their own incompatible wheels to fill in the missing bits. On X, there's enough flexibility for me to pick a DE and window manager separately, due to the standard modularization, whereas on Wayland, I have to check the compatibility of a screenshot tool with my desktop environment [1], and whether my DE even works with my graphics card! Everything becomes tightly coupled due to the lack of standards
[1] unlike some I actually do support the move to not let any app read the screen or global KB input, but the interface for those that do should have been part of the Wayland project, not just "not our department!"