The X Window System just turned 38: Down but not on its Way(land) out just yet
theregister.com
theregister.com
1) reliance on hardware acceleration which is not always available
2) The every frame being perfect thing (I far prefer having garbage on the screen temporarily if it lowers the latency for feedback. Latency makes me physically feel sick, I really really hate it.)
3) All the extra compositor specific crap for keylogging, screen recording, etc. It makes sense if you're building an Android competitor and expect people to carelessly throw binaries around but people don't do that on Linux.
But yes X is a great common denominator. I used it back in the 90s with Xappeal on DOS. Was great at college when we ran out of free X terminals.
> waypipe should be installed on both the local and remote computers. There is a user-friendly command line pattern which prefixes a call to ssh and automatically sets up a reverse tunnel for protocol data. For example,
waypipe ssh user@theserver weston-terminal
will run ssh, connect to theserver, and remotely run weston-terminal,
using local and remote waypipe processes to synchronize the shared memory
buffers used by Wayland clients between both computers.'shared memory buffers' sounds like an exploit waiting to happen though. Of course X11 is no better in this regard, an X-Client running on a remote X-Server has complete access to the remote display(s). But this is something that is unfortunately a design flaw from more naive times. And if there had been an X11R7 and onwards it would no doubt have addressed it.
I think part of the problem here is that the same people promoting Wayland have also taken X11 on board to 'maintain' so they have all the incentive to let it die. I'd have preferred to see an organisation that was ready to take it into the future.