Daniel Stone said:
Thus SoC and phone support isn't really a reason to not choose Wayland, not to mention that joining forces with Red Hat, Intel, etc by betting on a single display server - Wayland - would make it (much) easier and more realistic to get companies (including Nvidia/AMD) to write their (closed source) drivers with Wayland in mind.Every Mesa driver supports Wayland, plus numerous properietary drivers (mostly running on ARM)
Canonical knows this well, and the only reason that makes sense for them to create their own display server is to have full control of it - it also explains why they didn't contribute/complain/suggest/ask before anything about Wayland.
Last edited by mark45; 03-04-2013 at 07:52 PM.
Isn't there any fork yet?
I'm thinking there might be some miscommunication or something. Wayland is working with PowerVR, Qualcomm, Tegra and Exynos drivers as Ubuntu Touch is? That's surprising to me. Even still, I'd have to think that a massaged Android version is more mature than Wayland for these cases.
This is why I left Ubuntu and it's derivatives and am now pushing people i introduce to Linux to use alternative distrobutions. Ubuntu is going downhill pretty fast.
I think that for the desktop, the latter is the better option. But for the mobile space I think just a fork of Android's solution would be the best way to go, especially considering how they really want to ship products ASAP.
But converging both form factors into a single display tech is what gets me queasy. We've seen this rodeo played out a few times now and it doesn't end pretty.