All excellent points -
relatedly, noone is developing or releasing X windows applications *targeted* at these other platforms -
which is the same 'position' X will be in in this 'run x on wayland' world - further implying that over time
less and less applications will run on X, further implying that over time network transparency will
decrease more and more (since only the new firefox or libreoffice or whatever major software decides not to support X),
so this is a bad *direction* to be headed in.
I have no problems rearchitecting the X server infrastructure to have a fast low layer, and a simplified api talking
to this layer (that remains X, and therefore network-multiclient compatible), which is what most of the (non developer weenie)
people complaining about so-called 'crufty x' are talking about -
but don't !@#$ ruin out of ignorance and shortsightedness the good things in X because of the bad - fix the bad, and
make it compatible with what is.
ditto systemd, dbus and all of that stuff.
dbus? why not just f!@#$ing use the 127.0.0.1 loopback or require setting up a private multicast network????
nono, we need some crappy daemon writting using the hairball that is GLib-object-C being tied into *everything*
on the system.
derp derp derp.