Condorman wrote:I'm hoping that in the future it won't matter what you are running; be it X, Mir, or Wayland. I'm hoping the graphics vendors provide a driver for all occasions.
Sorry but regardless of the driver situation, it WILL matter. There will be compatibility issues between applications coded for Mir vs. applications coded for Wayland, even if we consider that most applications will use toolkits and thus be display-server-agnostic (assuming Canonical manages to keep all the toolkits supported downstream), there will still be applications that will not want or be able to use toolkits and thus will want to use the display server APIs directly. For example, consider games, and proprietary software that gets ported from other OS's, those are likely to use their own solutions for graphics, which will require them to write their own graphics backends, and those will only support one display server. In this case, the best possible scenario is, that they will use X, which is the lowest common denominator between Mir and Wayland. The worst, they'd use Mir, and their software would only work on Ubuntu, not on any other Linux, not even buntu derivatives.
Canonical's current plan to run a whole DE under XMir is plain idiocy, this arrangement has been shown to be slower than plain X in pretty much every situation, with no advantage whatsoever (the DE won't be able to use any of the advantages of Mir, since the X layer is in between). Running on plain Mir is impossible for other distros, since Mir is being designed in-house, for the needs of Unity only, with no regard for any other distro. It's no wonder that no other distro seems interested in using Mir in any way or capacity, and this will cause a situation where there will be Ubuntu, and then there will be Other Linux Systems - and there will be very little common between those environments. Canonical is building a walled garden, separate from the rest of the Linux ecosystem.