Hacker News

points by hollowonepl 2 days ago | 0 comments

I agree, this is also where I'm investing my time Metal mostly and then try to adapt it to DX12 on Windows and I totally skipped Vulkan for that simple reason you have described. but in generic terms only Vulkan comes with portability as analogy to original OGL vision.. I respect that even though the whole framework is to be ditched and rethought into something even more modern and sustainable...

so Metal yes, if somebody wants to be Apple focused. but in the academic world I don't believe that's the case either...

[–] pjmlp 2 days ago

Note that in regards to OpenGL original vision, game consoles never supported OpenGL, although some models kind of did support something, so game studios always cared about pluggable backends than targeting the one true API.

Only the FOSS community is so hard focused on Khronos APIs.

[–] swyter 2 days ago

Nintendo Switch 1 and 2 support both OpenGL 4.6 and Vulkan via the NVIDIA driver.

I've shipped a desktop OpenGL 3.3+ game sharing the same graphics code on Windows, Linux, macOS and Nintendo Switch. For example, worked just fine.

No translation layer overhead.

[–] pjmlp 2 days ago

It does, yet NVN is what matters for most studios.

A lucky scenario where you have not faced drivers issues, or extensions, that required multiple code paths.

[–] swyter 2 days ago

It really wasn't that big of a deal, to be honest. It's a relatively complex 3D commercial game shipping on PC and modern consoles, the FUD seems overblown.

Wondering if a ton of people are just repeating things they heard around instead of trying it themselves. Because OpenGL + SDL in 2026 is not 2011 OpenGL, and seems to work portably across the NVIDIA, AMD, Intel, Mesa, Apple drivers and more vendors I've tried first-hand.

[–] pjmlp 1 day ago

The FUD is such overblown that Godot had to implement a DirectX backend, when they only originally planned Khronos APIs, due to driver support issues they were getting.