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

Canonical gave a big fuck you to the Linux community for going with their own inhouse display server which causes fragmentation.

Mesa should give a big fuck you to Canonical by rejecting their Mir patches.

Sorry Canonical, but Wayland is the future.

Whatever happened to Linux being about choice? If a company wants to create their own display server, what's wrong with that? We should start putting restrictions on what display server you can use in Linux? That surely sounds pretty restrictive.

Mir and Wayland are both the future.

Should we start hating on Google now for not using Xorg or Wayland for Android and instead making their own?

Comment

Canonical gave a big fuck you to the Linux community for going with their own inhouse display server which causes fragmentation..

While it's true, that Canonical started all this, the same could be said vice versa about the Linux Community ever since Ubuntu started. If we really get fragmentation it's the fault of both not being able to work with each other, but instead blaming and rejecting (although most of the blame and rejections don't come from Canonical).

Comment

While it's true, that Canonical started all this, the same could be said vice versa about the Linux Community ever since Ubuntu started. If we really get fragmentation it's the fault of both not being able to work with each other, but instead blaming and rejecting (although most of the blame and rejections don't come from Canonical).

The problem is Canonical does not communicate with the community and its only getting worse they stated at the end of last year they will no longer dicuss future projects publicly.
The reason people are so mad at Canonical about Mir is they said they were going to use Wayland then started development of Mir behind closed doors and then suddenly announced it while saying they needed to use it because Wayland couldnt do certain things, however not once did they talk to the Wayland devs about these missing futures and as it turns out they were not missing at all.

So not I dont think the same could be said about the Linux community. Canonical has no interest working with others, just look at how much they contribute to upstream projects diddly squat.

Comment

The problem is Canonical does not communicate with the community and its only getting worse they stated at the end of last year they will no longer dicuss future projects publicly.
The reason people are so mad at Canonical about Mir is they said they were going to use Wayland then started development of Mir behind closed doors and then suddenly announced it while saying they needed to use it because Wayland couldnt do certain things, however not once did they talk to the Wayland devs about these missing futures and as it turns out they were not missing at all.

So not I dont think the same could be said about the Linux community. Canonical has no interest working with others, just look at how much they contribute to upstream projects diddly squat.

Canonical say to upstream you will do are bidding upstream Say's LOL you dont pay us