Linked by Thom Holwerda on Wed 5th Dec 2012 16:56 UTC, submitted by estherschindler
Thread beginning with comment 544325
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: But what does Wayland mean for Android?
by ThomasFuhringer on Wed 5th Dec 2012 19:44
in reply to "But what does Wayland mean for Android?"
RE[2]: But what does Wayland mean for Android?
by Morgan on Wed 5th Dec 2012 20:21
in reply to "RE: But what does Wayland mean for Android?"
I'm no developer, but I wonder if it would even scale up to desktop use. It's designed for one fullscreen app at a time; no window management would be possible without heavy modification.
And let's not forget what die hard X fanatics would miss the most: Remote X sessions. I've used them in the past from time to time, but there are some people for whom that feature is a necessity.
I may be wrong, but I think the best solution is to clean up and modernize X rather than shoehorn a mobile framework onto desktops. I don't have a problem with Wayland either, but I'm interested to see where the various distros go.





Member since:
2005-07-08
Android was the first major Linux-based client OS to ditch X11 in favor of a direct rendering manager (SurfaceFlinger). Now that Wayland inching its way toward adoption by Ubuntu and Fedora, what does this mean for the future of Android and SurfaceFlinger?
If Google has any intention of pushing Android upmarket into the productivity and workstation segments, then they may want a presentation framework which natively supports composited client windows. I suppose that ChromeOS, with its new Aura window manager on X11, would be the most likely venue for Google to introduce Wayland, if they have any intention of doing so.