Discussion
WebGPU question!
I've used GLSL/HLSL for a couple of decades now. I'm no wizards at it, but the syntax and data structures are rarely what gets in my way.
I've just started to scratch a little deeper than the surface of WGSL and.. wow.. is it me or is the syntax a massive PITA? Am I missing a trick? I guess I was expecting it to be closer to GLSL/HLSL at the "SL" level once I had all the binding stuff plumbed in and the basics were up and running :/
@evilpaul_atebit as someone who is considering getting into webgpu Some Time Soon Maybe, got some specific examples or gripes? I'm kind of curious
@halcy For example.. I just had to look up how to define output parameters in functions.
GLSL:
float myFunction(float2 x, inout int2 cell) {
cell = int2(1, 2);
return 1.0f;
}
WGSL:
fn myFunction(x: vec2f, cell: ptr<function, vec2i>) -> f32 {
*cell = vec2(1, 2);
return 1.f;
}
The GLSL just feels.. more intuitive. I fear that I'll get used to WGSL and then _really_ struggle to do any shader livecoding because all those platforms use GLSL :/
@evilpaul_atebit tbh, i wonder if there's just transpilers that go GLSL -> WGSL that you could just use if you didn't feel like dealing with that (but I guess maybe that leaves perf / features on the table)
@halcy @evilpaul_atebit Both the Tint and Naga WGSL compilers are able to ingest SPIR-V and emit WGSL. Naga also has a GLSL front end so it can do GLSL -> WGSL I believe. Not everything in SPIR-V can be converted, but we try to do as much as we can. The GLSLang compiler can convert GLSL to SPIR-V if needed. The DXC compiler can do HLSL -> SPIR-V.
@halcy No doubt. And no doubt :)
@evilpaul_atebit ouu, that's... I guess pretty.... rustlike?
@halcy I’ve not used any of the new fangled languages so I’ll take your word for it. I expected it to be more.. you know.. ECMAScript like 🤷
Install bonfire.cafe
Get the full app experience
