>>and implementing client and compositor support for it. It's exactly the same as X.
And if you think the GNOME and KDE and wlroots maintainers are all in some grand conspiracy, you are either very naively mistaken or just being toxic. Given you discarded a whole body of work as "ridiculously over-engineered" while contributing nothing except whinging, I'm inclined towards the latter.
Feel free to fork even one compositor and one client program to implement your amazing protocol.
> I already said:
> >>and implementing client and compositor support for it. It's exactly the same as X.
Not quite the same. X11 (notably the xfree86 project which maintained things for the last decade or so), was always quite free-wheeling about allowing things.
They subscribed to something similar to the linux kernels approach of "mechanism, not policy".
No, I don't think there is any conspiracy. Nor do I think they are bad people.
Nor do I think the whole thing is over-engineered. It's mostly pretty impressive.
But if you actually want to __use__ your extension/protocol with someone else, it needs to get accepted into various core libs and repositories.
....And then the gatekeepers step up and your problems start.