Hacker News new | ask | show | jobs
by shmerl 3417 days ago
You can simplify the design and reduce bloat if you don't need to address multiple APIs as backend.
1 comments
corysama 3417 days ago
To play devil's advocate: Isn't a big focus of web tech the goal of supporting multiple backends for everything? If a new platform wants to support WebGPU but not Vulkan (ex: XBone or PS4) it should be not just theoretically possible, but actively supported by the design of the Web spec.
link
ioquatix 3417 days ago
Good point.

But, that's assuming that it's not possible to write a wrapper on top of DX (for Xbone) that proves a Vulkan API. It's already been shown to be possible to do something similar, with MoltenVK.

The ball would be in Microsoft's court for this one.

link
corysama 3417 days ago
"it should be not just theoretically possible, but actively supported by the design of the Web spec."
link
douche 3417 days ago
> But, that's assuming that it's not possible to write a wrapper on top of DX (for Xbone) that proves a Vulkan API.

Is this not how Vulkan on Windows works? Given how many OpenGL drivers were just shims over DirectX in the past, I wouldnt be surprised if the same course was charted there.

link
shmerl 3416 days ago
No, it's pointless to do that. Why all the extra overhead? Vulkan talks directly to the hardware driver.
link
shmerl 3417 days ago
Could be, but PS and Xbox don't support Vulkan for the same bad reasons (lock-in), so messing up the spec because of that doesn't sound convincing.
link