Quote Originally Posted by garytr24 View Post
If wayland can do software rendering onto a remote X backend, acting as an X client, then the problem's solved, no?
From what I've seen on their mailing list, Wayland has no intention of supporting remote rendering, _AND_ they plan to have the applications do their own window decoration, which makes it fundamentally incompatible with X. They seem to want to take all the worst mistakes from Windows and repeat them.

Also, most apps will use an abstraction like QT or GTK, so will work with any backends supported by those.
a) that's a QA nightmare if you have to test every application with both X and Wayland backends.
b) having to tell every application whether to use X or Wayland would be a pain.
c) numerous applications simply won't work on X unless they're written to use it; most obviously anything that performs video playback. Not that video playback to a remote X server makes much sense of course .

To me, when the IT hype is heading back to the centralised server, thin client idea, throwing away all the features that were designed into X precisely in order to support that concept the last time it was going to be the future seems freaking insane.