Source

Thread

1/ @cmuratori

Shading language standardization for the web is completely f’ed. Even trying to follow the development process is basically impossible. Consider this post from 2018 (https://webkit.org/blog/8482/web-high-level-shading-language/), which is now completely false and all of the projects linked are now github 404’s.

Branches: 2021-12-21-datgame-how-would-you-feel-about-writing-shaders-in-rust, 2021-12-22-Aidiakapi-yeah-the-state-is-awful-and-the-shader-language

2/ @cmuratori

I guess originally they were going to do a sensible thing which was a modified HLSL for security guarantees, with a compiler. Now they are doing a text format that is “trivially convertible to SPIR-V” but without the SPIR-V part and no binary rep, I think?

3/ @cmuratori

I also tried to understand WTF was being claimed in http://kvark.github.io/spirv/2021/05/01/spirv-horrors.html but literally nothing the OP discussed seemed like anything resembling a “horror”. It just sounded like the learning process of someone who didn’t know SPIR-V learning SPIR-V?

Branches: 2021-12-21-Jonathan_Blow-i-read-this-page-and-its-very-bizarre-none-of-the