Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'll second that when Apple and MS will support Vulkan on their OSes and open codecs in their browsers. Or to put it another way, when they'll stop using sickening lock-in to make life harder for everyone.


They support Unreal and Unity.

Much better than supporting an API that requires 600 LOC for drawing a triangle and isn't available anywhere besides the reference platforms.


Supporting particular engines does not equal supporting open standards. It's not any better than zero rated services with ISPs. I.e. why should Apple or MS be gatekeepers for what engine should work and which shouldn't?

Apple at least is interested in Vulkan to some degree (they participate in Khronos). Whether it will show up on iOS is another question. But MS didn't show any interest. So claims that they changed their ways are premature.


So they just replaced OpenGL accelerated graphics stack by Metal and are still stuck on OpenGL 4.1 with lousy drivers.

Does this sound like a company that will embrace Vulkan, or a company joining the likes of Microsoft, Sony and Nintendo?


They started working on Metal before they knew AMD will give Mantle to Khronos to make Vulkan. So the open question is, whether Apple will support Vulkan or will sabotage it in order to preserve lock-in.

Unlike MS, Apple participates in Khronos Vulkan group if I'm not mistaken. Even Sony does. No idea about Nintendo.


Being part of Kronos doesn't mean they are forced to implement any of their standards.

Sony is a good example. The only Khronos stuff they use is WebGL in the PS4 menu and that OpenGL ES 1.0 with Cg shaders for the PS3 that no one used. All studios targeting PS3 favoured LibCGM (http://sandstormgames.ca/blog/tag/libgcm/).

But hope is good I guess.


They are actually listed as Vulkan participants: https://www.khronos.org/vulkan

No idea what they actually do, but if they'd add Vulkan support to PlayStation, it would be good for developers. Some Apple developers so far participated in SPIR-V / LLVM related discussions. And MS was notably absent in anything related.

As I said, when they'll fix this lock-in mentality, I'll second the claim that they seriously changed for the better.


Vulkan is still an abstraction. Most PS4 developers I know would prefer the stuff they already have which is closer to the metal. Something that uses the actual instructions for the PS4 GPU and not some cross platform API that then has to be translated to the actual GPU.

Yes, PS4 devs porting to PC would likely like Vulkan over OpenGL or DirectX but PS4 devs on PS4 not so much.


Making games for only one platform doesn't make sense since it limits reach, and using tons of incompatible APIs is annoying as well. Vulkan is low enough of an abstraction to perform quite well, so no matter what direction something can be ported, having a common API can save a lot of time.

Here is what some say about it: http://gamingbolt.com/ps4-should-support-vulkan-ps4s-api-not...


I didn't know that one could only use the browser that was installed on the system.


In case of Apple's iOS - only browser which uses their engine. Another sick lock-in example.


As far as Vulkan goes, that seems to be on the graphics manufacturers.


AMD makes chips for Xbox and PlayStation. And they contributed Mantle to Vulkan. But I doubt it's only up to them to actually support it on the corresponding OSes.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: