Originally posted by johnc
View Post
Announcement
Collapse
No announcement yet.
Intel Reverts Plans, Will Not Support Ubuntu's XMir
Collapse
X
-
Originally posted by intellivision View PostYou have to be kidding when you say an 'actual Linux OS' and not just several privately developed frameworks layered on top of each other rather than the freely available community frameworks available out there.
And there's also something that I don't trust about Intel, their past business dealings with SiS, VIA and AMD don't put them high in my support book.
Leave a comment:
-
Originally posted by DDF420 View PostSo normally we get **Canonical suck they never submit their changes upstream** to **Canonical suck because they submitted their changes upstream thus deserve to be rejected and no change should ever be accepted**?
The circle jerk shouting not to accept a patch to a video driver simply because its canonical is beyond the ridicules
Upstream won't take patches because other distros don't use it. Other distros don't use it because other DE's don't use it. Other DE's don't use it because it requires upstream patches that haven't been accepted. Upstream won't accept the patches because other distros don't use it................the linux community at its best
Fuckwits like Dee proclaim canonical are naughty children that deserve to be spanked simply for doing their own thing
No pleasing you lot
Anyway, no one is under any obligation to take Canonical's patches to help them create a one-distro solution for one desktop environment. Canonical themselves choose the path to go Mir, if they wanted collaboration and other people's help, there was already a very simple choice for them: use Wayland. That's the project chosen, by consensus, as the target for development as the next-generation Linux graphics system. Canonical is free to discard that option and make their own solution, but then it means that they can't just ask the rest of the community to do their work for them, if they want to go against the entire community and say "no, you guys are all wrong, we know better, things should be done our way" then they need to prove themselves and do all the work for it.
You can whine all day long about how people are evil for not doing Canonical's work for them, but in the end, if Canonical wanted collaboration, they should have gone with the project where people are already investing their work in, because that's the thing about free software, it's about choice. People get to choose where they put their work, and if Intel says they'd rather not put their work into maintaining patches for an unnecessary display solution that only benefits one company, instead of a display solution that benefits the entire community, that's their choice. Canonical also made their choice, now they have to live with it and put in the work.
Leave a comment:
-
Originally posted by Vim_User View PostLast I checked Chris Wilson, the one who submitted that rejected patch, worked for Intel, not Canonical. Your argument is invalid.
Leave a comment:
-
Originally posted by DDF420 View PostSo normally we get **Canonical suck they never submit their changes upstream** to **Canonical suck because they submitted their changes upstream thus deserve to be rejected and no change should ever be accepted**?
The circle jerk shouting not to accept a patch to a video driver simply because its canonical is beyond the ridicules
Upstream won't take patches because other distros don't use it. Other distros don't use it because other DE's don't use it. Other DE's don't use it because it requires upstream patches that haven't been accepted. Upstream won't accept the patches because other distros don't use it
Leave a comment:
-
Originally posted by dee. View Post
Dude, it was one rejected patch that shouldn't have been submitted in the first place. Canonical should have taken up maintainership of that patch in the first place, because that patch doesn't benefit anyone other than Canonical. It's not like Intel is actively hindering Canonical's plans on creating & using Mir, they're not actively making changes that would harm Mir's performance in any way. They're simply saying that if Canonical takes this road, they're free to do that, but they're not helping. Which is good, misbehaving children need to be set boundaries, otherwise they'll never learn.
And don't kid yourself, this decision doesn't affect anyone other than Canonical (not even them, really, as they can just maintain their own patch). No one else is ever going to use Mir. It's Unity-only, and everyone else will use X or Wayland. That's just the way it is, deal with it.
So normally we get **Canonical suck they never submit their changes upstream** to **Canonical suck because they submitted their changes upstream thus deserve to be rejected and no change should ever be accepted**?
The circle jerk shouting not to accept a patch to a video driver simply because its canonical is beyond the ridicules
Upstream won't take patches because other distros don't use it. Other distros don't use it because other DE's don't use it. Other DE's don't use it because it requires upstream patches that haven't been accepted. Upstream won't accept the patches because other distros don't use it................the linux community at its best
Fuckwits like Dee proclaim canonical are naughty children that deserve to be spanked simply for doing their own thing
No pleasing you lotLast edited by DDF420; 11 September 2013, 07:56 PM.
Leave a comment:
-
Originally posted by Vim_User View PostAh, then what you are really saying is: I don't know if Intel is making any money with supporting Android and Wayland, I just claim that they don't despite being able to back up that claim with facts. Glad we finally have settled that.
Leave a comment:
-
Originally posted by johnc View PostI'm sure they invest a lot of money in Android too... doubt they're making any money on it.
Leave a comment:
-
Originally posted by johnc View PostThen it really comes down to Canonical is just a small fish and gets different treatment because of that.
Leave a comment:
Leave a comment: