Comment 17 for bug 1149581

Application wise, it will not make much difference, as apps will target Qt, or Gtk+, or SDL
Toolkits must address the problem, not the apps (at least, not most of them).
Canonical already told the they will provide the support (and handle the burden, because, they create the 'problem', they have to deal with it).
The most sensible point, is drivers.
Up to know, Mir uses KMS/DRM , so, no change at all
My only worry is that wayland/weston and mir share the proprietary vendor drivers (nvidia, ati) .
Up to now, Canonical said that that will be the case (the drivers will be shared). But, it´s just talk, we don´t have _any_ proprietary vendor supporting mir _OR_ wayland.
Despite not liking canonical creating Mir (and how they did create it), they have the right, and I ´ll hold my judgement for when we start to see how things will got with proprietary vendor.
By then, if we see 'Mir only' drivers, then, I´ll agree that Canonical did really turn into a bad Apple (tm) on the basket, uninstall Ubuntu and Bash it until the day I stop breathing, when I´ll tell my son, at my death bed, to keep my legacy (bashing them) :P .
Despite all the crap we saw flying these days, I don´t think that will be the case (at least, I wanna believe that Canonical is better then Apple and Microsoft).