Mir 0.11 Working On Better Performance, Android External Display Support

[phoronix]

Phoronix: Mir 0.11 Working On Better Performance, Android External Display Support

Earlier this month we covered new Mir features that ended up being incorporated into the Mir 0.10 release. Mir 0.11 is now under development and it's already packing significant improvements...

http://www.phoronix.com/scan.php?page=news_item&px=Mir-0.11-Development-Features

[BlackStar]

Mir is shaping up to become a really cool X replacement.

At this rate of development, Mir will be delayed by another year...

[kaprikawn]

Mir is shaping up to become a really cool X replacement.

Wayland is the de facto X replacement. Mir is an X (or maybe Wayland?) alternative.

[Kemosabe]

At this rate of development, Mir will be delayed by another year...

Sadly, Wayland is not really faster ...

[TheBlackCat]

Sadly, Wayland is not really faster ...

Wayland protocol is basically ready, and the toolkits are mostly ready, now it is more a matter of desktop environments (none of which besides Unity will run on Mir anyway).

[BlackStar]

Sadly, Wayland is not really faster ...

Actually, it is. I have two Wayland (Arch) and Mir (Ubuntu) installations for development and Wayland is almost ready for day-to-day use. Check out the gnome/wayland wiki - it is not 100% there, but it's very close.

My personal experience is that Mir is significantly less stable than Wayland at this point in time, both in terms of system stability (crashes, corruption) and in terms of software stability (API/ABI changes).

The sad thing is that if Canonical would have been able to ship a stable Wayland in 14.10 if they had devoted their resources to that. With Mir, we are looking for a 15.10 release, if that.

[Pajn]

The sad thing is that if Canonical would have been able to ship a stable Wayland in 14.10 if they had devoted their resources to that. With Mir, we are looking for a 15.10 release, if that.

How come Canonical would have been able to release a stable version with Wayland ruffly a year before anyone else?

[Drago]

How come Canonical would have been able to release a stable version with Wayland ruffly a year before anyone else?

Not before anyone else, but along with anyone else. Efforts to develop Mir and porting GTK+ and Qt to Mir, would have gone to porting these to Wayland, and as a result everyone wins. I will hate to have the choice Wayland or Unity. I like them both.

[TheBlackCat]

How come Canonical would have been able to release a stable version with Wayland ruffly a year before anyone else?

Because everyone else is porting existing code-bases to Wayland while not breaking their existing X11 support. Canonical would have neither constraint.

Wayland is about a year ahead of Mir, according to Canonical's timeline. So if we trust Canonical's timeline, then if they had used Wayland it would have eliminated that extra year. Of course Canonical's timeline could slip again.

That is ignoring that without Mir Canonical would have additional manpower to either work on getting Unity working faster, or to work on getting Wayland ready faster, or to work on getting toolkits ported faster, or to work on getting related tools (like libinput) ready faster. I don't know which approach Canonical would have used, but any individual one of them or combination of them would have further sped up their timeline.

[Pajn]

Not before anyone else, but along with anyone else. Efforts to develop Mir and porting GTK+ and Qt to Mir, would have gone to porting these to Wayland, and as a result everyone wins. I will hate to have the choice Wayland or Unity. I like them both.

No, Wayland as a protocol have been more or less done for a longer time. The same effort to develop Mir would have been spent on developing a Unity Compositor for Wayland instead. The only difference is that they would have a strict protocol to adhere to.
Porting GTK+ and QT to Mir would have been free of course, but this is very small parts that haven't taken much developer time.

Because everyone else is porting existing code-bases to Wayland while not breaking their existing X11 support. Canonical would have neither constraint.

So it would have been a year faster to rewrite everything from scratch?

Wayland is about a year ahead of Mir, according to Canonical's timeline. So if we trust Canonical's timeline, then if they had used Wayland it would have eliminated that extra year. Of course Canonical's timeline could slip again.

[/QUOTE]Wayland isn't shiped as stable in any distro yet, hell even Gnome doesn't have stable support for Wayland for at least to April, and then it still haven been shiped as stable in any distro. Canonical plans to deploy Mir in less than a year and if that fails, in April next year.

That is ignoring that without Mir Canonical would have additional manpower to either work on getting Unity working faster, or to work on getting Wayland ready faster, or to work on getting toolkits ported faster, or to work on getting related tools (like libinput) ready faster. I don't know which approach Canonical would have used, but any individual one of them or combination of them would have further sped up their timeline.

It's about the same amount of work in any case, nearly no time would have been saved or lost if they had gone with Wayland. Tools like libinput can be used anyways and is planned to be used if they aren't already.