4 ms·
I find Apple's lack of commitment to Vulkan incredibly short-sighted on their part and downright offensive to developers. At a higher level, both Metal and Vulk
by wjakob 9y ago
I find Apple's lack of commitment to Vulkan incredibly short-sighted on their part and downright offensive to developers. At a higher level, both Metal and Vulkan address the same technical issues in previous APIs. The sheer waste of effort and squandered opportunities resulting from this type of fragmentation sometimes make me wonder if we need a regulatory agency to step in when big players show such obvious disregard for interoperability.
- mrec 9y agoBack around the end of February Khronos announced a "3D Portability" initiative [1], which would abstract over Vulkan/DX12/Metal. As I understood it, this could be a pure library solution which wouldn't require support from the platform and so would be less vulnerable to blockage by the usual walled-garden merchants. It was also mooted as a possible basis for WebGL-TNG. Unfortunately I've seen nothing but tumbleweed ever since, which makes me suspect that this is one of those Khronos initiatives that never makes it out of the hangar, much less off the ground. [1] https://www.khronos.org/3dportability https://www.khronos.org/3dportability
- tnoeu7nthoae 9y agoIf you want Vulkan on macOS, it exists [0]. [0]https://moltengl.com https://moltengl.com
- wjakob 9y agoThat's a commercial emulation layer -- this may be fine for some use cases but is definitely not a satisfactory state for the graphics ecosystem on Mac.