The assumptions that X11 uses are incompatible with what personal computing turned into. Drivers, security, the networking part... All of it is just not how things work these days.
It is a major project, it is hard to push through but it's there already, with most of the work complete by now.
And as a programer I must say that underlying Wayland libraries are vastly better than X11 ever was.
Maybe we should consider starting over again in that case. Wayland increasingly appears to be supported by a sunk cost fallacy itself - the A11Y issues are not fixable in the base architecture, which means that every Wayland DM implementation needs to implement them again, which in turn means lots of different APIs, incompatibilities and so on.
go ahead them, show was how to make a good screen protocol that is as secure as wayland, and flexible, and one that support every type of screen, from cellphones, to VR, to desktop, go ahead, i'm waiting, show how these wayland normies(x11 too, they are the same people) how to make a protocol
The assumptions that X11 uses are incompatible with what personal computing turned into. Drivers, security, the networking part... All of it is just not how things work these days.
It is a major project, it is hard to push through but it's there already, with most of the work complete by now.
And as a programer I must say that underlying Wayland libraries are vastly better than X11 ever was.