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.

Comment

And it won't be Mir. As Canonical stated, they develop Mir aimed especially for Unity, so everyone that does not use Unity (like Red Hat or Suse, you know, those companies that actually make money with Linux, unlike Canonical) will rather back up Wayland, since Mir may just break (intentionally or not) for other DEs. No sane company will make use exclusively of a product where they have no say about the development at all, so Wayland is naturally the way to go, not Mir.

Comment

since Mir may just break (intentionally or not) for other DEs. No sane company will make use exclusively of a product where they have no say about the development at all, so Wayland is naturally the way to go, not Mir.

Orly?
Let's just assume, Mir will be fucking awesome and will beat the shit out of Wayland:
Why exactly would anyone NOT use Mir and go for Wayland instead? If Canonical decides to go another direction, Mir can be forked and everyone is still happy.

Comment

I'm asking for it one more time - i know that your butts hurt, but stop this (pro|anti)(Mir|Wayland) nonsense. I'm a Ubuntu fan, I'm looking forward for UnityNext and Mir, but that's what happening on this forum (and not only) since Canonical's announcement is ridiculous, childish and pointless. Writing "Wayland" or "Mir" causes a chain reaction of shitstorm. Come on guys, is this the way the OpenSource community behaves?!

Comment

Why exactly would anyone NOT use Mir and go for Wayland instead? If Canonical decides to go another direction, Mir can be forked and everyone is still happy.

Because it's not collaboratively developed? Because contributing upstream requires signing contributor license agreement to Canonical that allows them to release it as closed source software? Because it's under L/GPLv3 that cannot be used in some environments? Because even if you fork it you still have to abide to the propietary Mir protocol and you are still stuck with the restrictive L/GPLv3 license (both Gnome and KDE are mostly under L/GPLv2 so they can't use the code from Mir without relicensing)? Because it's not written with other desktop environments in mind (in stark contrast to Wayland that's designed to be supported by multiple compositors)? Because its entire existence is entirely pointless in the first place? Mir will never be the only display server protocol because of the deliberate choises made by Canonical in terms of its licensing and design.

A large reason why Canonical gets all the shit it gets is because they are incapable of working in collaborative open source environments. Forking projects left and right. Not contributing patches upstream. Abusing their market dominance to create incompatible standards. Taking openly developed code behind closed doors and releasing it back months later with numerous additions without at any point contacting the upstream. Using contributor license agreements... and so on and so forth.