[cookiecaper]

I'm not sure why, but you seem unaware of the massive community effort that has already been plowed into Wayland and the massive loss of credibility the community suffers when it's wishy-washy about display infrastructure without Very Good Reasons. Qt and GTK have already been mostly ported, driver code has been contributed in various projects over the last 2-3 years, and other major efforts have been invested into Wayland to break the iron hand of X11, and then Canonical ignorantly struts along with Mir and jeopardizes the whole thing.

If we want big hardware players like nvidia and intel to take us seriously, we must behave in a professional manner, and one of the biggest players in the space creating an incompatible fork on such a fundamental piece of architecture five years after a similar project began making inroads, basically because "We don't have anyone smart enough to understand Wayland", is _not_ professional.

Maybe this would've been justified after Wayland support went mainstream, but all Canonical has accomplished by the release and announcement of Mir is the further entrenchment of X11 by accentuating what a horrendous wreck it is to attempt to remove it.