this article talks about the effect of the fork on Xorg itself. which is a very different topic, and one that is worth talking about.
for example i remember the fork of GCC and how it affected its development processes. unlike GCC i doubt that Xlibre will be merged back, but it has an influence on Xorg nonetheless. what are your thoughts?
the ideal outcome would be for Xlibre to become a testing ground for new ideas, where the good ones make it back into Xorg. but the planned obsolescence creates a conflict of interest for Xorg developers, and i suspect that new features will only be accepted reluctantly just to prevent Xlibre from gaining ground.
however, there is another potential outcome, in that the development of wayland focuses more on solving problems that prevent people from switching to it. now that would be a real win.
unlike GCC, X11 is on the way to obsolescence. and so one question is if there is even a point to continued development. but i also have the sense that Xorg devs would want to prevent Xlibre from growing. and the only way to counteract that is increased activity to show that Xorg is still under active maintenance, because the calls to replace Xorg with Xlibre are already coming, not just from those involved in Xibre but from others who are unaware of the drama and just see that Xlibre is actively maintained while Xorg isn't anymore (in their eyes).