PA is fine as long as you only need to do trivial things like watch videos, or listen to music, or such, where latency doesn't matter very much. When you need low latency, it's absolutely useless.
The fact is Wayland was endless Youtube demos of people showing flowers and shapes spin or colour changes. It took Mir's announcement months ago to get Wayland kicked into action and now we see progress.
(Look it up in Wikipedia! Make it like a fun game of learning!)
The fact is that Wayland has been in steady development for years, doing the groundwork for a modern display server. Just last year, it was 90% finished, and that's when Mir decided to jump off and take advantage of all that work. It's a good strategy, in a sense: hitch a ride until you're near the finish line, then jump off and sprint. At that point, Mir was announced, and then Wayland walked the extra bit to be complete, announced a stable protocol API, and things started progressing from there. It's not a coincidence, Mir just took advantage of all the hard work that looks slow to the observers, because of the lack of flashy demos, then jumped in right at the moment when the ride gets interesting. Of course it looks like the development gets faster in the end, because all the hard, slow, uninteresting bits are already done. The difference is, Wayland did those bits themselves, Mir just took advantage.
Others criticised Mir for its choice to use Android drivers, now we see Wayland users scramble to use libhybris even though Sailfish team instigated the basic form of the library and its connection to Wayland.
Obviously but why then did Monk get upset when his own team forked MeeGo, they use QT, Alien Dalvik, Wayland, etc. Then we had countless Wayland fanboys screaming blue murder that Canonical was shafting the scene.
Originally posted by Past Mark Shuttleworth
So that's the thing: having two competing display systems is harmful. Without Mir, the path would be clear: every distro could move on to Wayland, and legacy X software would still work via rootless application-specific X servers thanks to XWayland. All would be nice and simple. Anyone coming to bring their software to Linux would have it simple - develop it for Wayland, end of story. With Mir, everything just gets messy. Look at all the trouble it causes, for no benefit whatsoever.
Well now we can only hope the proprietary driver makers (Nvidia/AMD) pick the best display manager, else Wayland or Mir will be playing catchup. Personally I want Mir chosen as I'm yet to see any 'WOW' from Wayland. It's more like a XOrg rewrite. If the guy behind Wayland has his mission complete then it may be respectable, regarding speed and anti-screen tear.
Wayland is also far from a XOrg rewrite. If anything, Mir is closer to the structure of XOrg than Wayland. Mir is a server, like XOrg. Wayland is a protocol, that defines a way to build compositors, which can but don't have to be servers. Canonical could have built their own Wayland compositor, and have all the features they need, ones they want to do with Mir. Server side allocations, Android drivers, all of it. But they instead went the idiotic route of creating their own, incompatible system that no one else is going to use, ever, because no one else can use it. Because it's not useful to anyone else than Canonical, for reasons I already explained. So everyone else is going to use Wayland, and Canonical does their in-house thing because they decided to take a huge shit on the community.