Large Wayland projects like KDE and Gnome that are considered member projects of Wayland had the ability to NACK new wayland protocols and proposals. This has historically been abused by a lot of a different projects, in many instamces Gnome because they didn’t want to implement things. A lot of wayland proposals were unnecessarily delayed because of this. The bylaws of how wayland projects are allowed to NACK things has since changed to make it so a single project cannot needlessly block protocols but this was only implemented in the past few years iirc so for a long time this happened. Thats a massive contributor to why wayland development takes so long.
How outside of your fantasies did people bitching actually slow down devs introducing features that people should have known were needed in 2008?
Large Wayland projects like KDE and Gnome that are considered member projects of Wayland had the ability to NACK new wayland protocols and proposals. This has historically been abused by a lot of a different projects, in many instamces Gnome because they didn’t want to implement things. A lot of wayland proposals were unnecessarily delayed because of this. The bylaws of how wayland projects are allowed to NACK things has since changed to make it so a single project cannot needlessly block protocols but this was only implemented in the past few years iirc so for a long time this happened. Thats a massive contributor to why wayland development takes so long.
Linux desktop would be a lot further if the gnome project had died around the time 3.0 rolled out.