@(3) The Wayland transition was very disappointing. Needs from user groups as varied as (a) fractional-DPI laptop owners, (b) disabled users, (c) graphics apps managing floating palettes !! Were not considered early enough or thoughtfully enough. I don't see hard evidence there's a timeline for addressing them now.. I would call this a failure. But I need to be clear the failure was neither the decision to go Wayland, or the decision to do it now. It was a failure to plan ahead.
(4) Going forward, here is the problem that concerns me: Wayland withholds many capabilities apps had under X, reserving them for the compositor or extension designers. This would be fine if people could just pick the compositor with the features they need. But you don't get to pick your compositor because your compositor is bound to your DE. Compositors are fragmented, and fragmented in the way that holds back innovation rather than the way that promotes it.
If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/mcc/statuses/115838919481453534 on your instance and quote it. (Note that quoting is not supported in Mastodon.)