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

I tried it with Chrome Canary with the relevant flag but unfortunately it didn't seem to work with this particular site failing with "TypeError: Failed to execute 'createBindGroupLayout' on 'GPUDevice': required member entries is undefined.".

Shame as I wanted to see what happened if I pitted my desktop against it. Of course it's likely the WebGPU implementations between browsers are not equivalent from a performance point of view.



Unfortunately the browsers haven't quite settled on a standard, so the code posted only works in Safari.

More context here: https://news.ycombinator.com/item?id=22022962


It's pretty clear that SPIR-V should be chosen.


You may want to read this summary of the arguments pro and con SPIR-V, made by Kvark a gfx engineer at Mozilla, so you have a more balanced view of the topic :

The summary exists in two variants: a graphic summary[1] and a textual one[2].

[1] https://kvark.github.io/webgpu-debate/SPIR-V.component.html

[2] https://kvark.github.io/webgpu-debate/SPIR-V.html


WGSL has been chosen as of 2021, nothing more to discuss.

https://gpuweb.github.io/gpuweb/wgsl.html


> I tried it with Chrome Canary with the relevant flag but unfortunately it didn't seem to work with this particular site failing with "TypeError: Failed to execute 'createBindGroupLayout' on 'GPUDevice': required member entries is undefined.".

Firefox also raises the same error. It looks like Safari implements a former version of the WebGPU draft[1] where Chrome and Firefox implement a more recent one.

[1] :https://gpuweb.github.io/gpuweb/#dictdef-gpubindgrouplayoute...


They would show real usage performance though.

Still valuable.




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

Search: