> But now that you mention it, it's true that wayland was stagnating and that when Mir arrived, everything accelerated. Sometime having a common enemy is a good motivator.
This seems to be something a lot of people believe, but when you look at the history of it all it's really not the case.[1] I have a feeling it's because the controversy sparked a number of articles which talked about things in a more public way which made it feel like Wayland was suddenly making progress after stagnation, while in actuality development pace was chugging along as it always had been.
[1] Canonical announced Mir early 2013[2], you'll notice there is no great spike around that time in any of:
This is also in a similar boat. I'm having a hard time pinning down anything of any serious relevance from the GNOME/GTK side of things, but there is this[1] which shows that they had planned work on Wayland prior to the Mir announcement. It looks like they started actual work on it some time in 2013 which may look like it increased because of Mir, but I would tend to think that's more coincidence based on their prior plans.
From the Qt/KDE side of things we have work on QtWayland[2] and work on Plasma/KWin[3]. The former had development increase as work on Wayland continued and follows a general upward trend, especially after Plasma started using it. For the latter, the article covers the timeline pretty clearly.
From what I can tell my point still stands, even when talking about support from integrators.
[2] https://github.com/qt/qtwayland/graphs/code-frequency the spike you see happened Jan/Feb which was prior to the Mir announcement and if you check the number of commits there was no major increase at that time