Linux

My big complaint with Wayland is that the ecosystem has not really developed an effective standardization process.

With web browsers, you would get browsers doing their own thing; then copying each other's thing, then writing down a standard for that thing, then all switch to the standard.

With Wayland, you get: https://wayland.app/protocols/ For as old as Wayland is, there are 5 standard protocol extensions (plus some updates to the core protocol). A bunch sitting in the standardization pipeline. Then a whole bunch of redundant protocols because each compositor is just doing their own thing without even attempting to standardize.

It doesn't help that one of the major compositor (Gnome/Mutter) has essentially abandoned Wayland for everything beyond the core capabilities in favor of offering additional functionality over a separate DBus interface.