Eric's argument for why not to call it X12 is bizarre -- because if it were called X12 people who care about X might care about it, as if they won't care if it's called something else! A better reason for its not being called X12 is that it is clearly not an evolution of X11 in the way X11 was an evolution of X10: it's not a network protocol at all...
"Multi-monitors is a client problem". That's code for "a random half of your applications will eventually support your second monitor: the other half won't", and is just as broken as client window decorations for exactly the same reason. How this is better than X, where nothing but SDL (sigh, fixed in SDL 2) needed hacking for multiple monitors on my system, is not at all clear. (I have a good few (non-free) games that insist on rendering on only one monitor, which is reasonable, but every one of them without exception can be forced to render on a specific one and turn the other one off.)
Nobody uses core X, he says. My Emacs disagrees, it's running on a headless server using network transparency, plus client-side fonts, right now and working quite happily with very low volumes of network traffic and effectively instantaneous screen updates.
"A higher-performance version of VNC", the protocol in which scrolling a nearly-completely-black screen with a bit of text on it over a 1Gbps network takes half a second or so and is juddery as hell. Wonderful. (From other comments on LWN, I understand that VNC is not quite so bad anymore, and that this should be fixed 'properly' by having every single toolkit independently reimplement network transparency, only not a single toolkit has actually done that to my knowledge. Doubtless they will all use totally different authentication mechanisms and have their own network-related security holes. If they reimplement it at all, which I doubt.)
"Every frame is perfect". I don't understand why this is such an issue. Total amount of flashing or tearing I have had in X since I got a graphics card newer than an S3: none, not even when doing simultaneous overlapping textured video playback and oolite. I don't know what the hell the Wayland people are doing with X to make it tear all the time, maybe it's compositing. If compositing is making X creak at the seams this much, maybe a rethink is necessary, but personally given the choice between network transparency and wobbly windows I'd jump at network transparency every time.
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds