Linux community!? LOL. It's just two companies pie-throwing over the next display server. Nothing unusual in the corporate world, just in case you didn't know.
Originally Posted by verde
Labeling others as 'fanboys' doesn't diminish their arguments or make you look more objective.
Originally Posted by Pajn
There is valid arguments against Conanical's choice to use their own DS, and it doesn't just involve emotional attachments to one tech or the other.
Good thing I'll be sticking with NVIDIA.
Originally Posted by jrch2k8
i dont get this why bash Intel for removing a Junk Patch that was developed for Political Gain thats why the shitty Mir server was developed Troll Blog
It is a bit laughable to accuse Intel of politics, when the entire Mir inception amounts to a 100% pure political move since Mir adds /nothing/ technologically, yet he fails (or deliberately omits) to see that.
Originally Posted by phoronix
And then calls on Intel to be mature. Sure, Intel can forgive Canonical, so long as Mark Shuttleworth scraps his Mir plans and moves over the developer efforts toward bringing Wayland and XWayland to the desktop, and switches back to his original commitment. Should Intel take on Canonical's responsibility of maintaining their patches because Mir users might potentially expose bugs that can be patched up upstream? To me that is a barely tenable argument... because Wayland users - of which there will be thousandfold more (if not even more), will have exposed every bug in every nook and cranny of the Wayland source code and the Intel GPU drivers.
All due respect to Luc - but he is posturing and adding nothing new to this discussion. Canonical made their bed, now they need to lie in it.
Originally Posted by MartinN
Maybe they can get the X bugs ironed out first.
Even on Windows the Intel drivers and GPUs are a bit of a joke.
for some reason people think wayland is an independant product that got out few X developers asses for simple fun or masochism, what you fail to see is that every project in the graphic stack was rewritten to make wayland possible[and mir] aka KMS/DRM/DRI2,3/Gallium/mesa/drivers architecture/TTM/libpciaccess/xkb/pixman/and many other related projects because wayland was literally impossible to make with the previous graphic stack.
Originally Posted by johnc
more simply put every line of code made in the last 5 years to the graphic stack in kernel and userspace was with the goal of creating wayland, wayland is the final piece needed to complete the graphic stack upgrade[aka the usable user side API for toolkits] even more simply wayland didn't take 5 years of ultra carefully slow protocol design, rewrite the entire graphic stack to make wayland possible took 5 years.
To be fair (and i'm no X11 expert) X11 doesn't really have so many "bugs" as it has "architectural flaws".
Originally Posted by johnc
I was more referring to Intel's X drivers.
Originally Posted by F i L
The idea that in due time (and soon) every bug will be ironed out of Wayland and Intel's driver is kind of silly.