If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Don't forget that Mir is totally unneeded here as XMir does all the compositing. All Mir does is receiving the rendered image from XMir and printing it on the screen (like a full screen window). So in fact X is doing all the work here and Mir is just a unneeded layer.

Don't forget that Mir is totally unneeded here as XMir does all the compositing. All Mir does is receiving the rendered image from XMir and printing it on the screen (like a full screen window). So in fact X is doing all the work here and Mir is just a unneeded layer.

well in the case of xwayland it actually faster than native Xorg due to the way wayland works[i explained 400 times look for it in the forum] but in the case of XMir is not clear since even if do thing similarly is still quite different compared to wayland, beside wayland support a wide set feature that aren't still present[or ever will] in Mir that really helps certain operations to happen with lot less roundtrips like EXA.

as other thing Mir don't support bufferage extension that im aware of, so im not sure how they will deal with VSync and partial damage on screen when compositing

i guess it will be test and see[not me tho i don't give a rat ass about ubuntu anymore, gentoo is my mistress now]

The Kubuntu developer is right. There is literally zero reason to use Mir right now. X will continue to be supported in the mean while, so running Kubuntu on XMir is just adding an additional potential source of bugs for no benefit. It makes no sense to do so. If there are some Mir-specific programs that would be very useful on Kubuntu, the issue could be revisited. On the other hand, by that time KDE Frameworks 5 will probably be finished, thus Wayland will be the obvious choice for them.