Linked by Thom Holwerda on Mon 9th Sep 2013 21:22 UTC, submitted by lucas_maximus
X11, Window Managers Intel on Ubuntu's XMir:

We do not condone or support Canonical in the course of action they have chosen, and will not carry XMir patches upstream.

Ubuntu has to do virtually all its work on Xmir drivers by itself. No one else supports it.

Thread beginning with comment 571660
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by aaronb
by Auzy on Mon 9th Sep 2013 23:48 UTC in reply to "RE[2]: Comment by aaronb"
Auzy
Member since:
2008-01-20

If I had to fathom a guess, I'd be guessing its because everyone else is backing Wayland at the moment, and, Mir is simply going to fragment the community.

Also, I believe that Ubuntu originally backed Wayland, but changed their mind.

This is actually a VERY good move long term for Linux. Yes it will make things bad for Ubuntu. However, as both Mir and Wayland uses different code, supporting both would lead to a significant amount of development hours wasted globally (which could be spent on making Linux more competitive, and bringing wayland up to parity with Xorg).

I also believe that Wayland was announced ages before Mir. If this is true, it is irresponsible for Canonical to steam ahead with their own solution.

Reply Parent Score: 1

RE[4]: Comment by aaronb
by Delgarde on Tue 10th Sep 2013 01:16 in reply to "RE[3]: Comment by aaronb"
Delgarde Member since:
2008-08-19

Also, I believe that Ubuntu originally backed Wayland, but changed their mind.


Oh yes, they were the most enthusiastic of supporters of Wayland a while back... Shuttleworth declaring that Ubuntu would be running natively on it a couple of releases ago.

Then nothing much happened to deliver on that boast, and eventually it was revealed that they'd started their own competing project that they'd been working on in secret for the past year... supposedly because Wayland had a bunch of imaginary defects that made it unacceptable for them (similar defects, oddly enough, to the ones that Mir got caught with in one of the earlier previews).

Reply Parent Score: 6

RE[5]: Comment by aaronb
by Lennie on Tue 10th Sep 2013 11:55 in reply to "RE[4]: Comment by aaronb"
Lennie Member since:
2007-09-22

Actually, Canonical proposed Wayland changed the way Wayland handled multitouch and Wayland didn't want to change.

So Mir now exists.

That is what happened (as far as I know/understand it).

Edited 2013-09-10 11:55 UTC

Reply Parent Score: 4

RE[4]: Comment by aaronb
by Sauron on Tue 10th Sep 2013 05:34 in reply to "RE[3]: Comment by aaronb"
Sauron Member since:
2005-08-02

If I had to fathom a guess, I'd be guessing its because everyone else is backing Wayland at the moment,


Who is everyone else?
Apparently AMD have stated they won't be supporting Wayland. This leaves Intel who is, and Nvidia who haven't said yet. If Nvidia do support Wayland I guess their sales will go up while AMD's fall, but only in small amounts which don't matter to them I suppose.

Reply Parent Score: 3

RE[5]: Comment by aaronb
by lucas_maximus on Tue 10th Sep 2013 11:27 in reply to "RE[4]: Comment by aaronb"
lucas_maximus Member since:
2009-08-18

Their Catalyst drivers won't. But the open source AMD driver will.

Reply Parent Score: 4

RE[5]: Comment by aaronb
by Neolander on Tue 10th Sep 2013 18:58 in reply to "RE[4]: Comment by aaronb"
Neolander Member since:
2010-03-08

I guess he was talking about every vendor who has actually made some kind of move to push Linux display technology forward.

I say this because as far as I know, AMD and NVidia's current plan is to stick with Xorg as long as they'll be able to get away with it. Which kind of makes sense, since it's not as if they would make any money out of the effort of going through a Wayland- or Mir-friendly driver rewrite.

Edited 2013-09-10 19:02 UTC

Reply Parent Score: 3

RE[4]: Comment by aaronb
by andydread on Tue 10th Sep 2013 10:41 in reply to "RE[3]: Comment by aaronb"
andydread Member since:
2009-02-02

If I had to fathom a guess, I'd be guessing its because everyone else is backing Wayland at the moment, and, Mir is simply going to fragment the community.

Also, I believe that Ubuntu originally backed Wayland, but changed their mind.

This is actually a VERY good move long term for Linux. Yes it will make things bad for Ubuntu. However, as both Mir and Wayland uses different code, supporting both would lead to a significant amount of development hours wasted globally (which could be spent on making Linux more competitive, and bringing wayland up to parity with Xorg).

I also believe that Wayland was announced ages before Mir. If this is true, it is irresponsible for Canonical to steam ahead with their own solution.



So let me get this strait. If submit patches to your project and you refuse the patches and tell me to go pound sand. So i sit down at my desk and write my own code. Now its irresponsible that I didn't use your code? Who the hell are you to dictate to anyone what code they should or shouldn't write?

Reply Parent Score: 3