3 ms·

Maybe Apple will stop the nonsense and support the Vulkan API, too.

by mtgx 9y ago

tzahola 9y ago
Haha, dream on!
anfilt 9y ago
Made think of this. It's from the Vulkan Programming guide. https://imgur.com/gallery/1pxYT https://imgur.com/gallery/1pxYT
zanny 9y ago
An AV codec isn't a weapon to lock developers into your platform while wasting millions of dollars and thousands of man hours on pointless api ports. There are too many implementations of encoders / decoders for the various formats lying around to get away with that. Its not like they didn't try with Quicktime in the past (ish? .mov was just a crippled .mp4), but that never really made them any money I don't think.
- CharlesW 9y ago
  > .mov was just a crippled .mp4 That's backwards — Apple contributed the Movie file format as the basis of the MPEG-4 file format.[1] [1] https://en.wikipedia.org/wiki/MPEG-4_Part_14#History_of_MP4 https://en.wikipedia.org/wiki/MPEG-4_Part_14#History_of_MP4
- ComputerGuru 9y ago
  mov significantly predated MP4
m_eiman 9y ago
Metal release date: 2014 Vulkan release date: 2016 (announced 2015) So since somebody made a non-compatible clone a couple of years later, Apple should have ditched their work and lost the power to make decisions as they see fit in the process? That doesn't sound like something that would appeal to them.
- vetinari 9y ago
  Unfortunately, the 2014 Metal release is not comparable to 2016 Vulkan release. Metal from 2014 had a lot of assumptions (for example, that the GPU shares memory with CPU), so it could be released earlier due to being simpler. That's why it was supported only on iOS. And that's why there were more Metal releases and refinements. Apple had to make improvements to make it equal in its capabilities to Vulkan 1.0 and DX12.
dmitriid 9y ago
Why would they? They invested heavily in their own API (Metal) while OpenGL committee was sitting on its ass doing nothing, and released it a year before Vulkan was even announced.
linopolus 9y ago
Why should they? Metal works wonderfully on all their platforms. Besides, Metal also predates Vulkan..
proyb2 9y ago
You know Vulkan often changes or update their spec? It's not a nonsense for Apple to develop their own with easier API also made for Swift language, reliability is important. In fact, Metal is powered in all iOS SDK too.

Maybe Apple will stop the nonsense and support the Vulkan API, too.

by mtgx 9y ago

Maybe Apple will stop the nonsense and support the Vulkan API, too.

tzahola 9y ago

Haha, dream on!

anfilt 9y ago

Made think of this. It's from the Vulkan Programming guide. https://imgur.com/gallery/1pxYT https://imgur.com/gallery/1pxYT

zanny 9y ago

An AV codec isn't a weapon to lock developers into your platform while wasting millions of dollars and thousands of man hours on pointless api ports. There are too many implementations of encoders / decoders for the various formats lying around to get away with that. Its not like they didn't try with Quicktime in the past (ish? .mov was just a crippled .mp4), but that never really made them any money I don't think.

CharlesW 9y ago
> .mov was just a crippled .mp4 That's backwards — Apple contributed the Movie file format as the basis of the MPEG-4 file format.[1] [1] https://en.wikipedia.org/wiki/MPEG-4_Part_14#History_of_MP4 https://en.wikipedia.org/wiki/MPEG-4_Part_14#History_of_MP4
ComputerGuru 9y ago
mov significantly predated MP4

m_eiman 9y ago

Metal release date: 2014 Vulkan release date: 2016 (announced 2015) So since somebody made a non-compatible clone a couple of years later, Apple should have ditched their work and lost the power to make decisions as they see fit in the process? That doesn't sound like something that would appeal to them.

vetinari 9y ago
Unfortunately, the 2014 Metal release is not comparable to 2016 Vulkan release. Metal from 2014 had a lot of assumptions (for example, that the GPU shares memory with CPU), so it could be released earlier due to being simpler. That's why it was supported only on iOS. And that's why there were more Metal releases and refinements. Apple had to make improvements to make it equal in its capabilities to Vulkan 1.0 and DX12.

dmitriid 9y ago

Why would they? They invested heavily in their own API (Metal) while OpenGL committee was sitting on its ass doing nothing, and released it a year before Vulkan was even announced.

linopolus 9y ago

Why should they? Metal works wonderfully on all their platforms. Besides, Metal also predates Vulkan..

proyb2 9y ago

You know Vulkan often changes or update their spec? It's not a nonsense for Apple to develop their own with easier API also made for Swift language, reliability is important. In fact, Metal is powered in all iOS SDK too.