It Looks Like Canonical Will Soon Publish Vulkan Mir Support On Mesa

[phoronix]

Phoronix: It Looks Like Canonical Will Soon Publish Vulkan Mir Support On Mesa

We've been waiting to see Vulkan on Mir after the developers working on this display server for Ubuntu missed their original Ubuntu 16.04 target but the latest chatter indicates we might be seeing the support materialize soon...

http://www.phoronix.com/scan.php?page=news_item&px=Vulkan-Mir-Is-Closer

[blackout23]

Why do Mesa and Mir need special support to get Vulkan running on Mir, when it works on Wayland from Day 1?
https://www.collabora.com/about-us/b...t-for-wayland/

[microcode]

Why do Mesa and Mir need special support to get Vulkan running on Mir, when it works on Wayland from Day 1?
https://www.collabora.com/about-us/b...t-for-wayland/

Because Canonical just couldn't keep out of the compositor protocol game. If they would work together, or at least with the same protocol, they would be shipping by now.

[cj.wijtmans]

Because Canonical just couldn't keep out of the compositor protocol game. If they would work together, or at least with the same protocol, they would be shipping by now.

Canonical wants to be the new micro$oft. They are trying so hard.

[tegs]

Canonical wants to be the new micro$oft. They are trying so hard.

It's not like the Wayland team is a bunch of cavalier programmers trying to help the greater good. It's backed by IBM and Red Hat, which are bigger corporations than Canonical.

[cj.wijtmans]

It's not like the Wayland team is a bunch of cavalier programmers trying to help the greater good. It's backed by IBM and Red Hat, which are bigger corporations than Canonical.

but did IBM and red hat install spyware into their OS like Canonical did with ubuntu/unity?

[cj.wijtmans]

Honestly they should have continued upstart since systemd just likes to absorb everything and become a memory hog with its logging "journal" system and ditched Mir for wayland... everyone would have won. But no they do opposite.

[Scias]

Honestly they should have continued upstart since systemd just likes to absorb everything and become a memory hog with its logging "journal" system and ditched Mir for wayland... everyone would have won. But no they do opposite.

This article has nothing to do with systemd so please crawl back to your Veteran Unix Admin ® cave and complain there. Plus what you say makes no sense as they would also have to swim against the current and waste resources should they have kept developing upstart in the same way than the Mir vs Wayland story.

Anyways good luck to them for convincing Mesa to upstream and maintain a Mir-specific codepath.

[A-Singh]

but did IBM and red hat install spyware into their OS like Canonical did with ubuntu/unity?

"Spyware"... lol.

[Scias]

PS: Please remove this "unapproved" bullshit. This is getting out of hand.