| |||||||||||||
Wayland and Weston 1.0 releasedWayland and Weston 1.0 releasedPosted Oct 26, 2012 8:17 UTC (Fri) by dgm (subscriber, #49227)In reply to: Wayland and Weston 1.0 released by jschrod Parent article: Wayland and Weston 1.0 released
> We're replacing "XYZ" that does "ABC", calling it "xyzzy".
Strawman. Wayland does not replace X11. X11 can be run on top of Wayland, just like it does on Windows or OSX. The rest of the argument does not make sense.
(Log in to post comments)
Wayland and Weston 1.0 released Posted Oct 26, 2012 8:25 UTC (Fri) by jschrod (subscriber, #1646) [Link]
> Wayland does not replace X11.
When Qt und GTK focus on Wayland, these DEs will have native Wayland applications, and X will not be a first class citizen any more. It will only be supported as an legacy interface. As long as we don't want to be stuck using current software versions, that means that de-facto Wayland *will* replace X11 in the medium-to-long term.
Besides, the experience of running X11 on Windows or OS X is no good advertisement, either. I've done both, and good integrated support is something different.
Wayland and Weston 1.0 released Posted Oct 26, 2012 9:32 UTC (Fri) by paulj (subscriber, #341) [Link]
This is rubbish. Qt and GTK are not DEs, but toolkits. Further, these toolkits *both* have long supported rendering outputs *other* than X11 for a long time (from Windows GDI to direct framebuffers, even HTML). So there's just no basis to say that the addition of another rendering context, Wayland, is going to change the quality of X11 support.
The only thing that could change that is if X11 becomes so little used that no one cares to support it anymore.
|
|||||||||||||