2 ms·

The answer was fairly clearly stated right from the beginning. [quote]Canonical chose the latter., with Mir built specifically to meet the aims and goals of Un

The answer was fairly clearly stated right from the beginning. [quote]Canonical chose the latter., with Mir built specifically to meet the aims and goals of Unity.[/quote] Where the goals of Unity was convergence across all platforms. http://www.omgubuntu.co.uk/2013/03/canonical-announce-custom-display-server-mir-not-wayland-not-x http://www.omgubuntu.co.uk/2013/03/canonical-announce-custom... A lot of people chose not to believe this, but it doesn't change the fact that the Ubuntu team clearly articulated that they thought that their goal of convergence across several form factors required a new display server which was focused more on that than Wayland.

Etzos 10y ago
It's not that people chose not to believe this, it's that the whole point doesn't make sense at all when looked at in detail. When asked to provide specific technical reasons for the existence of Mir beyond the nebulous ones stated in the article, Canonical was unable to list anything of any real value. Input was one of the things mentioned, but in the end they ended up going with the Wayland solution (libinput). The whole point of Mir's existence, that is a goal of convergence across several form factors, is also filled perfectly by Wayland. Mir provided no advantages over Wayland for that goal. This is kind of frustrating because Canonical spent time working on a system which provided almost exactly the same thing as Wayland instead of contributing to Wayland. And that alone may not have been that bad if they had been open about it, but Mir development happened in the dark for a long time prior to announcement and when it finally was announced Canonical listed off a bunch of issues they had with Wayland which they had never even brought up with the Wayland developers. All that would probably still be okay if at the end Mir offered something over Wayland, but that's just not the case. Even now there doesn't seem to be any technical reason for Mir to exist or have existed at all.

Etzos 10y ago

It's not that people chose not to believe this, it's that the whole point doesn't make sense at all when looked at in detail. When asked to provide specific technical reasons for the existence of Mir beyond the nebulous ones stated in the article, Canonical was unable to list anything of any real value. Input was one of the things mentioned, but in the end they ended up going with the Wayland solution (libinput). The whole point of Mir's existence, that is a goal of convergence across several form factors, is also filled perfectly by Wayland. Mir provided no advantages over Wayland for that goal. This is kind of frustrating because Canonical spent time working on a system which provided almost exactly the same thing as Wayland instead of contributing to Wayland. And that alone may not have been that bad if they had been open about it, but Mir development happened in the dark for a long time prior to announcement and when it finally was announced Canonical listed off a bunch of issues they had with Wayland which they had never even brought up with the Wayland developers. All that would probably still be okay if at the end Mir offered something over Wayland, but that's just not the case. Even now there doesn't seem to be any technical reason for Mir to exist or have existed at all.