For me the move to QT is a good thing, I mean QT is no longer fully closed source and is freely used in KDE/ Razor QT
Plus QT apps in general are way better then GTK ones.
Developing a display server is one thing. Getting 20+ years of applications to suddenly be compatible with it is what takes time.
Somewhat related question here: If Unity transfers to Qt/qml will Ubuntu then see a default software shift as well, I'm thinking Rhythmbox --> Amarok?
"Act only according to that maxim by which you can also will that it would become a universal law." - Immanuel Kant
"Beware of he who would deny you access to information, for in his heart he dreams himself your master." - Pravin Lal
So why use a untried untested thing like wayland?
Most applications have nothing to do with X. They are dependant on the toolkit (Qt & Gtk). Once you port the toolkits to Mir, almost all the applications will automatically be compatible. The few applications that use X directly, will be supported by launching rootless X session.
My findings may be entirely preferential and apply only to me and nobody else, but I do have to honestly question from an unbiased standpoint how something supposedly "inferior" can still look and feel superior in every way. Sure you can polish a dog turd and you still have a dog turd in the end, but I can say even as a KDE lover that I've certainly had less issues in GTK land than any Qt oriented land I've spent time in. My 2c.
Canonical's Mir Project Retracts Wayland Criticism
About effin time. Regardless of what happens, this undertaking is huge and I have great hopes for it. If any one has ever had any incentive for getting the ball rolling, and the means to do so, is Canonical and Ubuntu.
Hopefully, this will mean that Unity can actually turn into a really fast and fluid experience instead of suffering the limitations in which it's stuck with now.
For all purposes, X is all good and wonderful, but something better is needed for the future.