Once we've got an Ubuntu LTS and a RHEL/CentOS release out there with Wayland by default, X11 ought to rapidly become a thing of the past. There's Xwayland, but with any luck that'll become something you basically never use, just like happened with Xquartz.
I use Linux at work since 1999 and I have used a local display less than 1% of the time.
An application that does not work remotely does not exist for me.
For all other uses, you always have xwayland [1], until they adopt the new guy.
I have provided support to Nederlands and Portugal using X11VNC.
Outside work, my wife and my mother are using linux. They call me when they have an issue. Hopefully, I can help them remotely 99% of the time.
IMHO, local desktop is the exception in entreprises.
It's convenient to have access to the desktop session I left running the night before remotely if I want to. I mostly use it to sync files/code I forgot to upload when I quit the last time, or to start a download on Steam or something like that.
I'm sure Wayland will eventually support similar usage, but I understand you reluctance to adopt it until it does.
Of course, the option is right there on the login screen to start an X session instead, if Wayland doesn't work for you.
In contrast, AMD is actively contributing to the open source amdgpu driver.
Can you give a source for this? I'd be very much interested in trying out Plasma on Wayland on NVIDIA, but I can't find any information about NVIDIA implementing GBM.
This is just anecdote of course! I would have liked to dig more into it and figure things out, but honestly I just had too much to do and chose whatever was working for me.
You might need to find new ways to accomplish a few tasks, though. But I can attest it works.
Edit: fix desktop/compositor confusion
EDIT: Well, I just checked and it turns out I am not running the wayland session! I will have to investigate why...
How so?
The only issue I had was Synaptic was crashing. Other than that I have fewer crashes and hangs on wayland compared to X
The answer is no.
Mir 0.28 landed just in time for 17.10, as a sibling linked. This version includes basic Wayland support.
A read over Mir/Spec [0] shows that though they don't want Wayland to be at the core of Mir, they want to be able to talk and integrate with it at a higher level.
It should be noted that Mir is only installed by default on Ubuntu Touch, and probably won't be integrated into the desktop by default until Unity8 is ready.
[0] https://wiki.ubuntu.com/Mir/Spec?action=show&redirect=MirSpe...
Huh? As far as I can tell Unity8 is never going to be ready. The exact words from Mark Shuttleworth were "we will end our investment in Unity8, the phone and convergence shell".
Clearly there are still people working on Mir, it's had ~200 commits in the past month. But I'm confused as to who's left using it.
Ubuntu Touch still exists but seems badly starved of development resources. I haven't followed it too closely other than occasionally flashing onto my old Nexus 4 to check things out but it seems like there's barely been any progress in the past few years, and Canonical dropping their support surely isn't going to help matters. I would love to be wrong about this but the project seems to be barley limping along. Ubuntu Phone is also still based on 15.04 and in the process of transitioning to 16.04 so it seems like it'll take ages for these Mir improvements to land.
But, some of Mir's utility carried over into Canonical's IOT stuff.
No one I've spoken seems to know why Mir still has an active team after the big changes.
There's some speculation of MATE adopting when Mir hits 1.0, but it really is speculative.
I don't know why, but Mir marches on. I doubt we'll see it on desktop anytime soon.
They look like they have only had half a dozen bugs lodged in the last six months. Doesn't seem too vibrant for an actively-developed desktop.
Mir on the other hand, looks quite active.
The Wayland protocol apparently made some bold decisions to enforce security through isolation, and apart from the compositor it is all but impossible for anything to sneak a peak at what other programs are doing visually. It'll be interesting to see if that causes users a problem.