4 ms·

The built-ins are named inconsistently, aren't visually any different from other parts of the code, and the change from sets to groups when there are workgroups

The built-ins are named inconsistently, aren't visually any different from other parts of the code, and the change from sets to groups when there are workgroups makes no sense. All around change for the sake of change.

jsheard 2y ago
> All around change for the sake of change. More like change for the sake of politics, Apple didn't want to use any Khronos IP so the WebGPU committee had to work backwards to justify inventing something new from scratch, despite the feedback from potential users being overwhelmingly against doing that. Then after sending the spec on a multi-year sidequest to develop a shader language from scratch, Apple still hasn't actually shipped WebGPU in Safari, despite Google managing to ship it across multiple platforms over a year ago. Apple only needs to support Metal.
- davexunit 2y ago
  Apple has been extremely slow about getting important features into Safari. They're about a year behind Chrome and Firefox on some WebAssembly things, too.
  - jsheard 2y ago
    Safari's limitations are baffling sometimes, like it's the only browser that doesn't support SVG favicons aside from a non-standard monochrome-only variant. Their engine supports SVG, just not in that context, and you'd think they would be all over resolution independent icons given their fixation on extremely high DPI displays.
    - pjmlp 2y ago
      On the other hand, they are the only wall left standing between the old Web and ChromeOS everywhere.
- flykespice 2y ago
  Apple is the epitome of Not Invented Here syndrome.
- rahkiin 2y ago
  I’ve read this is because they are in a legal conflict with Khronos for a while already
- jdashg 2y ago
  > the WebGPU committee had to work backwards to justify Do you mean to allege "[the Apple delegates to] the WebGPU committee"? Because the committee as a whole has a ton of public minutes that show how strident the opposition to this was. (Probably filed under "This is not a place of honor" :)) I don't even want to re-read what I said at the time. No one involved, literally no one, is happy about that chapter, believe me. We are happy to be shipping something, though.
- pjmlp 2y ago
  Blaming Apple is cool and all, yet Vulkan also uses GLSL, which WebGPU committee could have kept using for WebGPU, as evolution from WebGL, just like it happened on the OpenGL to Vulkan transition.

jsheard 2y ago

> All around change for the sake of change. More like change for the sake of politics, Apple didn't want to use any Khronos IP so the WebGPU committee had to work backwards to justify inventing something new from scratch, despite the feedback from potential users being overwhelmingly against doing that. Then after sending the spec on a multi-year sidequest to develop a shader language from scratch, Apple still hasn't actually shipped WebGPU in Safari, despite Google managing to ship it across multiple platforms over a year ago. Apple only needs to support Metal.

davexunit 2y ago
Apple has been extremely slow about getting important features into Safari. They're about a year behind Chrome and Firefox on some WebAssembly things, too.
- jsheard 2y ago
  Safari's limitations are baffling sometimes, like it's the only browser that doesn't support SVG favicons aside from a non-standard monochrome-only variant. Their engine supports SVG, just not in that context, and you'd think they would be all over resolution independent icons given their fixation on extremely high DPI displays.
  - pjmlp 2y ago
    On the other hand, they are the only wall left standing between the old Web and ChromeOS everywhere.
flykespice 2y ago
Apple is the epitome of Not Invented Here syndrome.
rahkiin 2y ago
I’ve read this is because they are in a legal conflict with Khronos for a while already
jdashg 2y ago
> the WebGPU committee had to work backwards to justify Do you mean to allege "[the Apple delegates to] the WebGPU committee"? Because the committee as a whole has a ton of public minutes that show how strident the opposition to this was. (Probably filed under "This is not a place of honor" :)) I don't even want to re-read what I said at the time. No one involved, literally no one, is happy about that chapter, believe me. We are happy to be shipping something, though.
pjmlp 2y ago
Blaming Apple is cool and all, yet Vulkan also uses GLSL, which WebGPU committee could have kept using for WebGPU, as evolution from WebGL, just like it happened on the OpenGL to Vulkan transition.