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.
The whole Wayland vs. Mir is just fanboys and hatred.
People who care about the technology doesn't rely care.
Labeling others as 'fanboys' doesn't diminish their arguments or make you look more objective.
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.
is backwards, is certain that intel won't touch Mir, so canonical will have to maintain their own mesa branch to make Mir support intel drivers, aka the burden of support the hardware is back to canonical which is the one with the genius idea of make Mir in the first place, not intel in the upstream driver that have noting to do with canonical decisions.
so like is working today ubuntu will provide a mesa packages will all the neccesary patches to support open drivers in Mir and regular mesa will have wayland support by default thats is all this decision means
Phoronix: Luc Verhaegen Comments On Intel/Mir Politics
Luc Verhaegen, the former RadeonHD graphics driver developer at SUSE and now working on the Lima project for reverse-engineering ARM Mali graphics, has shared his thoughts on the recent developments surrounding Intel backing out their XMir driver support...
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.
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.
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.
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.