Originally posted by Pajn
View Post
Announcement
Collapse
No announcement yet.
Luc Verhaegen Comments On Intel/Mir Politics
Collapse
X
-
Originally posted by Pajn View PostThe whole Wayland vs. Mir is just fanboys and hatred.
People who care about the technology doesn't rely care.
No one gets hurt by having a competition if the competition plays by the rules with Intel now didn't.
Comment
-
Originally posted by TheBlackCat View PostWhat specific rules have Intel broken?
Comment
-
Originally posted by mrugiero View PostYes, I commented before reaching half of the article, my bad on that. However, you stopped to make an article about that, while I don't recall you mentioned Canonical as an example in the previous article, while you did mention Intel proves your point now. Both of them proved your point.
Also, as I discussed in the original thread about Intel reverting the patch, even though it's ugly that the management gets to choose about it, they are paying those devs, and they don't want them to maintain that support (even if the patch is trivial) on their money. If the ones maintaining it will be from Canonical, then it's probably easier for them to just skip all of the upstream revisions and just get it out of tree, so I think Chris shouldn't have done the patch in the first place, until it stops being a one distro solution, since until then it makes more sense in downstream. Of course, one could argue he did it in his free time, but I think if that's so, he should state it, so every discussion about Intel here will be over with the "they rejected a free patch just because of politics" statement.
Comment
-
Originally posted by mark45 View PostNo it's not, unless you're a drama queen type. It's stupid for Intel to support a product of a different company which directly competes with its own product (Wayland devs are paid mostly by Intel/Red Hat). Folks, this is not socialism where anyone has to be nice to the point of supporting its own competition, it's about winning and making money, get real.
This is what every open source company does, on the surface they pretend they're nice and "share" everything they can with everybody (call it neo-socialism or whatever) but in reality every open or non-open source company only cares about growing profits, market expansion and crushing the competition. There was never a time "when companies were good".
Comment
-
Originally posted by Honton View PostYou need to do more than writing the patch. You need tp prove you will be there for the entire life time to maintain it. If not you can't do that it will become Intel's burden. They have solid reasons to back out of this. Canonical can pick up the patch if they like such non-CLA code.
Also, I mentioned several times already that they can pick up the patch, and that I do think it belongs to downstream. This doesn't change the fact management choose politics over technical reasons. On the technical side, I will always trust more the maintainer than the manager, and I do that because the maintainer is usually someone trained to pay attention this technical details, while management is trained to evaluate more on the costs/benefits side.
Originally posted by libv View PostTBH, I thought that Intel was in the business of selling hardware, and that therefor providing good driver support should be their prime concern. Reinventing the X server, or fighting battles over such things, should be less of important. With this move intel seems to have forgotten about this niggle.
Comment
-
Originally posted by mrugiero View PostI'm really tired of this kind of comments. I'm giving free testing to Canonical's Mir, so please stop calling me a hater (and don't deny you did, because you clearly generalized to everyone who tries to make sense out of it). The fact is I care about the technology, and that's why I don't bitch about all of the other NIH syndromes around open source (including the whole systemd/upstart situation), because most actually bring some differences. This time, it introduces more severe fragmentation (I'm aware it's partially alleviated by toolkits), and I'm still waiting to see any reason for it. Also, I'm completely against running DEs on XMir because I care about the technology, and specifically I care about friends who will be using this technology. That's also why I test it whenever I can. Luckily, my flavor of choice won't use it in 13.10.
nor Wayland have any built in toolkit. All renderings are done to buffers and buffers
alone. And because of that no software like xclock or xcalc will be written for any
of the as that simply isn't possible. Toolkit is what will be used and if a toolkit
supports both your app bill support both.
And I don't know what running a DE in XMir have to do whit any of this. If you
think it's pointless then god don't do it, nobody cares.
Comment
-
Originally posted by libv View PostTBH, I thought that Intel was in the business of selling hardware, and that therefor providing good driver support should be their prime concern. Reinventing the X server, or fighting battles over such things, should be less of important. With this move intel seems to have forgotten about this niggle.
Given Intel's history with open source, I'm inclined (though certainly with eyes opened) to believe there's a valid reason behind droping XMir support until proven otherwise.
Comment
-
Originally posted by Pajn View PostNo having Mir and Wayland doesn't introduces severe fragmentation. Neither Mir
nor Wayland have any built in toolkit. All renderings are done to buffers and buffers
alone. And because of that no software like xclock or xcalc will be written for any
of the as that simply isn't possible. Toolkit is what will be used and if a toolkit
supports both your app bill support both.
Bugs found and fixed on Mir aren't going to be bugs found and fixed on Wayland and vice-versa, therefore fragmenting efforts.
Comment
-
Originally posted by libv View PostTBH, I thought that Intel was in the business of selling hardware, and that therefor providing good driver support should be their prime concern. Reinventing the X server, or fighting battles over such things, should be less of important. With this move intel seems to have forgotten about this niggle.
you could argue they support android but the solid truth is they did so because they see profit in that platform and choose to support it, it wasn't google forcing intel.
google since they bought android they keep their specific android only code downstream and only upstream the non android specific code which from my POV is the proper professional way of doing things, you assume the cost of your fork and contribute back all the useful code for everyone else to keep the community support[i know they aren't exactly perfect at it but at least they try].
beside mir situation im sure intel don't support hurd, bsd, amigaOS, genode, etc. either
Comment
Comment