Mir Display Server Lands API Changes, Relicenses Headers To LGPL

[Vistaus]

wow i booted live cd of Ubuntu 17.04 (Zesty Zapus) Daily Build with Unity8 and it sometimes looks more broken than Wayland on Gnome but at least there is native mir chromium based browser and some nice polished tablet friendly user interface, memory usage is also much better. The whole thing crashed after hitting PrintScreen key.

There's also a Wayland port of Chromium already available from AUR. Chromium also merged part of the code the AUR build uses (ozone) into their main code, so they're working on it.

[lucrus]

I sincerely and badly hope Canonical fails in its Mir goals. Their blatant arrogance deserves yet another public failure. Had they contributed the same efforts to Wayland, at least starting from about two years ago, when it was already clear Mir is a sinking ship, today we would already have Wayland in every Linux desktop.

[starshipeleven]

to allow inline functions in headers without forcing users to gpl3. but everyone else apart from Canonical can't freely move code between header and source, lol

Fixed. CLA allows them to move code wherever they like as they can relicense stuff you contributed. It's you or any other downstream projects that can't do the same.

Considering that Mir has like 0 downstream projects and is used only by Canonical already for a bunch of other very valid reasons, this is not going to matter much. Another brick in the wall, so to speak.

[TheBlackCat]

Considering that Mir has like 0 downstream projects and is used only by Canonical already for a bunch of other very valid reasons, this is not going to matter much. Another brick in the wall, so to speak.

Chicken and egg problem. Projects that might be inclined to at least support Mir are less likely to do so because of the CLA stuff.

[starshipeleven]

Chicken and egg problem. Projects that might be inclined to at least support Mir are less likely to do so because of the CLA stuff.

if with "support" you mean adoption, kinda yes. CLA is not liked, and also the fact that MIR happened after most have already decided to go with Wayland.
If with "support" you mean make applications that run in it too, kinda no for open applications. Afaik major toolkits already support MIR so in most cases it's not going to be hard to support it.

But for closed applications it will be fun. I suspect that they will keep running on xorg (or xwayland or xmir) for a long while, as that's the only way they can run on both MIR and Wayland.