| |||||||||||||
Wayland and Weston 1.0 releasedWayland and Weston 1.0 releasedPosted Oct 26, 2012 4:44 UTC (Fri) by dlang (✭ supporter ✭, #313)In reply to: Wayland and Weston 1.0 released by rahulsundaram Parent article: Wayland and Weston 1.0 released
nobody is saying that your ability to run X applications is going to go away soon.
But we are concerned that the ability to run an X based desktop is going to go away
compatibility with wayland is a one-way street.
if the app is written for wayland it can talk to wayland
if the app is written for X it can talk to wayland
this is being excused by claiming that the major graphics toolkits support both, so you will never find an app that is wayland-only
I'm saying that this is only the case until some toolkit maintainer decides that it's "too hard" to continue to support X, after that, all software that uses that toolkit will be wayland-only.
If they were to make a shim layer that would let a wayland-only app show up on an X desktop, they would go a long way towards relieving this concern.
(Log in to post comments)
Wayland and Weston 1.0 released Posted Oct 26, 2012 6:12 UTC (Fri) by mjg59 (subscriber, #23239) [Link]
Any remoting solution would work just as well in proxying Wayland-specific apps onto X desktops.
Wayland and Weston 1.0 released Posted Oct 26, 2012 11:34 UTC (Fri) by daniels (subscriber, #16193) [Link]
> If they were to make a shim layer that would let a wayland-only app show up on an X desktop, they would go a long way towards relieving this concern.
Weston has had, pretty much since day one, a really competent nested-under-X11 compositor backend. It works pretty much like Xephyr, in that your desktop is rooted rather than being window-by-window, but it works great.
If the clamour of people who genuinely need X11 and cannot live with anything else is so great, a solution for this will definitely emerge.
Wayland and Weston 1.0 released Posted Oct 27, 2012 8:41 UTC (Sat) by paulj (subscriber, #341) [Link]
Apps are not "written for X11" today. They're written in some toolkit library, like Qt, GTK+, and the toolkit arranges the rendering (possibly via another library). Apps in the future will continue to be written to use toolkits. So "if the app is written for Wayland" is just a straw-man.
Apps in the future will continue, overwhelmingly, to be written to one of a small number of toolkits. At least some of these toolkits, including the 2 most popular, *already* support multiple rendering outputs (from X11, to Windows, to direct framebuffers, even to HTML!). Hell, they *already* support Wayland!
Your fear is unfounded. You can relax, your apps will, overwhelmingly, continue to work with X11, Wayland, whatever, without you or your apps having to care. X11 will continue to work, even if fewer people use it.
|
|||||||||||||