Wayland was created by X11 developers, as they decided keeping X11 going was beyond hope.
Feel free to find volunteers to fulfill their shoes.
Feel free to find volunteers to fulfill their shoes.
The real work was done in the 80s/90s through a consortium of universities and corporations
Then one day, some nobody shows up and in their infinite wisdom decides: I know better than all the 100s of people before me.
And now we have to listen on and on about how this nobody was somehow a "major developer"
Wayland exists because, thanks to hardware innovations, there's a better way to do the job than what was possible in the 80s.
>> Wayland exists because, thanks to hardware innovations, there's a better way to do the job than what was possible in the 80s.
E.g. instead of the Xwayland approach, you could've already ditched "half" of Xorg if you stripped most of the server-side drawing primitives and server-side font support and moved them to Xlib, handling it client side, and then made it clear someone else would need to take over maintenance of Xlib, and "started over" with a stripped down Xcb.
You could've validated further restrictions by letting clients opt in to them with extensions before "flipping the switch" and restricting them by default when the damage was acceptable.
Even if we then eventually reached a point where there'd be a schism, odds are it'd be far smaller. And certainly far less time would've been wasted.