s/systemd/Wayland/g
s/2014/2015/g
s/systemd/Wayland/g
s/2014/2015/g
I understand part of the issue was Canonical changing their support for Wayland, but what exactly does Mir do to make developers lives harder? Most developers don't write for X directly, nor will most developers write for Wayland or Mir directly, so as long as the library support is in place then why should we care? I don't hear Android developers complaining about Android using its own window manager. If Canonical want to pay extra for their own window manager, and are prepared to work on the libraries that make developers lives easier, what are we really losing?
Yes, their best interests. Not to the Linux ecosystem.
From what I've gathered, we have, as a community gained a lot from that by looking at Red Hat Inc, Canonical Ltd, SuSE GmbH/Novell/Attachmate Group and others contributions.