[shmerl]

If I understand correctly, they'll drop the server part replacing it with Wayland. But they'll keep their compositor, which any Wayland based DE needs to implement anyway. They don't intended it for the desktop, since they are dropping Unity. It's for IoT and etc.

[DC-3]

I hardly think that Mutter is the be-all and end-all of Wayland compositor performance. I could see Ubunu plumbing a re-moulded Mir back into their distribution further down the line (while keeping the rest of the GNOME environment). I'm not certain on the technical details, but I believe this should be possibly; for Wayland was certainly designed with compositor agnosticism in mind.

Edit: reading further, it appears that GNOME Shell is quite tightly woven into Mutter, which may well complicate matters.

[simion314]

GNOME devs realized already that they have problems with the current architecture, I think X got the blame though this time too, so they plan a GNOME4 version, I do not know if they started coding it or are just in planing phase.

[simion314]

They can't replace something with Wayland because Wayland is a protocol and interface, Mir needs to implement code to speak that protocol.

[shmerl]

OK, then they are replacing the compositor and changing their client, rewriting it to talk in Wayland protocol.

[simion314]

They are no removing a Mir component and add a Wayland component, they implement the Wayland protocol on top of existing code, maybe refactoring where it is needed, so Mir could talk wayland and still do the Mir stuff that is needed for IoT.