4 ms·

this is a good point, and I'm quite curious what the hit will be. Safari makes it substantially easier to enable WebGPU than Chrome does (requiring a canary ve

this is a good point, and I'm quite curious what the hit will be. Safari makes it substantially easier to enable WebGPU than Chrome does (requiring a canary version and flags), which leads me to believe there's already some security mechanisms in place. But, time will tell!

captainbland 6y ago
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.
- brrrrrm 6y ago
  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 https://news.ycombinator.com/item?id=22022962
  - rubatuga 6y ago
    It's pretty clear that SPIR-V should be chosen.
    - pjmlp 6y ago
      WGSL has been chosen as of 2021, nothing more to discuss. https://gpuweb.github.io/gpuweb/wgsl.html https://gpuweb.github.io/gpuweb/wgsl.html
    - littlestymaar 6y ago
      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 https://kvark.github.io/webgpu-debate/SPIR-V.component.html [2] https://kvark.github.io/webgpu-debate/SPIR-V.html https://kvark.github.io/webgpu-debate/SPIR-V.html
- rovr138 6y ago
  They would show real usage performance though. Still valuable.
- littlestymaar 6y ago
  > 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-gpubindgrouplayoutentry https://gpuweb.github.io/gpuweb/#dictdef-gpubindgrouplayoute...

captainbland 6y ago

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.

brrrrrm 6y ago
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 https://news.ycombinator.com/item?id=22022962
- rubatuga 6y ago
  It's pretty clear that SPIR-V should be chosen.
  - pjmlp 6y ago
    WGSL has been chosen as of 2021, nothing more to discuss. https://gpuweb.github.io/gpuweb/wgsl.html https://gpuweb.github.io/gpuweb/wgsl.html
  - littlestymaar 6y ago
    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 https://kvark.github.io/webgpu-debate/SPIR-V.component.html [2] https://kvark.github.io/webgpu-debate/SPIR-V.html https://kvark.github.io/webgpu-debate/SPIR-V.html
rovr138 6y ago
They would show real usage performance though. Still valuable.
littlestymaar 6y ago
> 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-gpubindgrouplayoutentry https://gpuweb.github.io/gpuweb/#dictdef-gpubindgrouplayoute...