That is the point, they stated publicly that Wayland was the future, which was a dick move. However, while wayland was at 1.0 by the time they announced Mir, Gn

That is the point, they stated publicly that Wayland was the future, which was a dick move. However, while wayland was at 1.0 by the time they announced Mir, Gnome and KDE were far from using Wayland in production. Even today, I do not use Wayland on Gnome because it doesn't support hot reloading of the compositor, Intel's work on bringing a native Wayland frontend to Chromium is MIA. But I guess my contemporary gripes with Wayland have nothing to do with Mir and everything to do with the fact that Wayland was just a protocol that a number of independent parties had to agree upon and implement correctly. Even today, Nvidia doesn't want to play ball when it comes to Wayland compositors interfacing with their proprietary drivers. Whilst commit frequency does not display this, I still believe that developing Wayland was taken more seriously after Mir was announced. This is however my suboptimal opinion, and I am willing to concede that I am wrong and discuss the matter further.