The Wayland Situation: Facts About X vs. Wayland (Phoronix)

And BTW take it to kronos, what ever gets to be a kronos standard is the one that will win.

I like the idea for compatibility
http://hack.org/mc/texts/gosling-wsd.pdf

Something very simple, even perhaps CoreX11 is too much (don't know), the remote case i would keep the protocol and download a conformant piece to every machine... its client, everybody downloads VNC etc if they wanted.

Most important of all take it kronos... let me see, about **ALL** the industry is there (fame and jobs).

The reality is that you are getting obsolete gentleman, the arguing is intense, but you seem to have lost the boat. Input(X) is bad ? ... what about streaminput ? ( i know NIH)... composition ? there is already a OpenWF http://www.khronos.org/openwf/ ( yes i know NIH) GL ? ... well they are at OpenGL4.3, the all edifice is being build around EGL i think (Linux DS is based on whatever fix for a problem seems the best by a few heads in a particular time, irrespective of others)

X, Wayland, MIR ??? ... i think this isn't going anywhere.

Perhaps Android DS can became full industry compliant (Kronos), and we can scrap all that s**t, no matter if many think that in point A or B their lady is much better.

If everybody coding for X (apps) could continue that would be awesome, but that is the only reason i see to give them the trouble to adopt another window system and protocol... **standard and lasting**... techs particularities are terceary importance, after all software can change all the time(to where is what might not be the wise thing, even if some tech argument is valid)

(it has do to with philosophy, complex systems above the "animal" don't evolve by competition, natural evolution crap, they destroy each other instead, like animals that eat each other... the natural paradigma of the human relation is cooperation not animal fagomania)