Discussion
I'm currently writing compute shaders directly in wgsl but I'm thinking about maybe replacing it with something backend agnostic.Slang is looking good on the surface, is it good in practice? Anyone got experience with it or recommendations for something else?
I don't know if I need it really, but two reasons would be being backend agnostic, and getting features like include etc. (I can do a simple version of the latter myself though.)
@SonnyBonds not really 😁 all 'standard options' have massive dependencies (e.g. for Slang see: https://github.com/shader-slang/slang/tree/master/external).
glslang + spirvtools + spirvcross + tint is "tiny" in comparison (for sokol-shdc I'm planning to drop tint in favour of this spirvcross-fork with wgsl backend: https://github.com/ludicon/spirv-cross-wgsl
@floooh Oof, yeah. Might stick to just plain wgsl with a custom include sys or something on top then.
Thanks for weighing in.
@SonnyBonds ...that reminds me, wasn't there some "extended WGSL" thingie which added stuff on top of vanilla WGSL...
Yo, it's this: https://wesl-lang.dev
@floooh I'm guessing you may have thoughts on this?