>This is the worst path Canonical could have possibly chosen. Now developers across all different toolkits and applications, from Gtk+ to Wine, will need to mai

>This is the worst path Canonical could have possibly chosen. Now developers across all different toolkits and applications, from Gtk+ to Wine, will need to maintain massive patchsets to integrate with Ubuntu. Either that or run in a rootless X window in "legacy" mode. >This will not end well for interoperability, for developers, or for the wider Linux ecosystem. Bad times. That comment on OMG! Ubuntu! is making me uncomfortable with the consequences this might have for the GNU/Linux ecosystem. I am not sure about how far I can trust that comment, but the Phoronix article[1] explains it better: >Canonical developers will make to see that applications relying upon Qt/QML, GTK3, XUL, etc will be able to use Mir in an "out of the box" manner. The legacy X support will come from an in-session root-less X Server. I would, though, like to know more about the consequences for this. First of all, we know that Unity will be much faster, since this thing needs to run on phones too and Unity will actually be a "real thing" instead of just a Window Manager (Compiz) plugin. >Isn't a point of FOSS that people can all contribute to one major project instead of reinventing the wheel? That is another comment on OMG! Ubuntu! and I completely agree with it. Sure, freedom of choice is great, but why not use Wayland, really? It was designed from scratch to work for everybody. [1]: http://www.phoronix.com/scan.php?page=news_item&px=MTMxNzI http://www.phoronix.com/scan.php?page=news_item&px=MTMxN...