Okay so if nobody should work on abstracting GPU APIs in browsers, what about native? Given current APIs as fixed, do you endorse efforts to try to write a hardened abstraction over them, or just give up and everyone writes for each platform manually?
-
The representation could be an already-existing one (e.g. SPIR-V if you think that is okay), or a modification of that, if judged to be good enough. But the point is to push the ball in the right direction instead of the wrong direction.
I am suspicious of SPIR-V (look at all the weird special hardcoded stuff that's in there already), but have not used it so won't comment.
-
-
The design goal of WGSL is that conversion to/from SPIR-V should be straightforward and lossless. We at least got Apple to not object to that. And then it has the gross garbage that up-translates that to all the various shading languages.
-
So you'll be able to use SPIR-V as your instruction set if you can stomach that conversion step. I'm hopeful that someday that step could be eliminated, at least in WebGPU implementations outside the browser. And SPIR-V already has driver-level support of course.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.