Vulkan Support Still Isn't Ready For Ubuntu's Mir

[phoronix]

Phoronix: Vulkan Support Still Isn't Ready For Ubuntu's Mir

Back in February when Vulkan launched as the new Khronos graphics API, Ubuntu developers planned to have Vulkan support in Mir by Ubuntu 16.04 LTS. That didn't happen and since then it has kept getting pushed back...

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

[arboy84]

When is Canonical going to stop throwing good money after bad and end development of Mir? Is saving face really worth that much money? Is there any technical reason not to switch to Wayland?

They could branch libweston and play catch up within a year.

[duby229]

Sometimes corporations make marketing claims before they actually understand what the market is. That's what happened here. Canonical would have to renege on a few important marketing claims. Even though it would be the best thing for them is they actually did, they won't.

[davidbepo]

When is Canonical going to stop throwing good money after bad and end development of Mir? Is saving face really worth that much money? Is there any technical reason not to switch to Wayland?

They could branch libweston and play catch up within a year.

actually there is one: wayland is a protocol and mir is a server (like xorg) so in mir more features can be shared while in wayland EVERY compositor has to implement them so the work is duplicated, libweston should help with that though

[theghost]

Guys, please have faith. As soon as we have Unity 8 with Mir as the default, we can finally have Vulkan support. And with soon, I mean very soon, it's just a matter of a few years. It will be sooooo great, really.
Meanwhile look at Canonical's great success on the mobile front or IOT. They are simply everywhere...

[om26er]

When is Canonical going to stop throwing good money after bad and end development of Mir? Is saving face really worth that much money? Is there any technical reason not to switch to Wayland?

They could branch libweston and play catch up within a year.

You are funny, not really. Canonical knows what its doing, its the other gang' stuff which only takes pace when Canonical introduces an alternative. Mir is running on a number of mobile phones for more than a year that are being sold in the market. I assume, if money really was an issue at Canonical, Ubuntu would only exist for the server.

The real issue is not Canonical, its the other gang which wants a central control on all things Linux platform.

[schmidtbag]

What I don't understand is why bother with Vulkan? Desktop compositors aren't complex enough to warrant this kind of attention right now. That isn't to say Vulkan should never be added, I'm just saying there are far more important things that users actually care about. Canonical doesn't have infinite resources and this is isn't a small task.

[starshipeleven]

actually there is one: wayland is a protocol and mir is a server (like xorg) so in mir more features can be shared while in wayland EVERY compositor has to implement them so the work is duplicated, libweston should help with that though

Wat? Mir is just a compositor using a different protocol, so what features are shared with who?

[starshipeleven]

You are funny, not really. Canonical knows what its doing, its the other gang' stuff which only takes pace when Canonical introduces an alternative. Mir is running on a number of mobile phones for more than a year that are being sold in the market. I assume, if money really was an issue at Canonical, Ubuntu would only exist for the server.

The real issue is not Canonical, its the other gang which wants a central control on all things Linux platform.

Wow, so much total bs.

[davidbepo]

Wat? Mir is just a compositor using a different protocol, so what features are shared with who?

afaik mir implements more things in server side than wayland, although i could be wrong

for now there is only a mir compositor, (the unity one), but features could be shared IF they were more compositors