News for hackers. Stuff that matters.
Re:The state of Mac gaming by wjakob on Monday July 17, 2017 @01:56PM (#14790847)
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.
Re:The state of Mac gaming by mrec on Monday July 17, 2017 @02:06PM (#14790936)
Back 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

Re:The state of Mac gaming by tnoeu7nthoae on Monday July 17, 2017 @04:37PM (#14792077)
If you want Vulkan on macOS, it exists [0].

[0]https://moltengl.com

Re:The state of Mac gaming by wjakob on Tuesday July 18, 2017 @07:36PM (#14800945)
That'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.