Basically bunch of stuff listed in that blog are Rust specific uint vs int.
Others are kinda standards problem of undefined behavior being well - undefined. Gamedevs are used to this, but not Rust devs.
I'm reminded of xkcd https://xkcd.com/927/
So rather than relying on previous work, they wrote their own somehow ugliest standard.
- Not knowing you need to have entry point for the shader to be executed.
- kvark's complaint about OpFmod being misnamed are kinda missing the point, % isn't the mod operator but remainder operator (in C/C++)
- https://mobile.twitter.com/TheSpydog/status/1232819839888166... You know it's a pretty bad idea when Unity and Adobe are begging you not to do this.
- I mean what you prefer to write?
GLSL:
int a = 2
for (int i = 0; i < 4; i++) {
a *= 2
}
WSGL: const a: i32 = 2;
var i : i32 = 0;
loop() {
break if (i >= 4);
a = a * 2;
continuing {
i = i + 1;
}
}I'm also really not sure how you got the first point from what he wrote. He was not saying he was surprised to find "you need to have an entry point" he was saying the restriction made no sense, and that existing tools didn't even take advantage of having more than one entry point due to driver bugs.
The rest of your points are basically just opinions masquerading as something else. In any case I don't actually care how hard WGSL is to write, because I don't have to write it (you can go through a translation layer). What I'm not going to do is pretend that SPIR-V is a great choice for this intermediate layer solely on the basis of what I've heard from other graphics people who haven't actually tried to use it for that purpose--which is exactly what the article is about.
> he was saying the restriction made no sense
So presented with reality of a complex, buggy drivers, his solution is - to ignore it? Wow imagine in UTF-8 people just said, yeah 8bit 0 are ok everywhere and caused hundred of billions of lines of code to be written to deal with null mid UTF8 stream.
> I don't actually care how hard WGSL is to write
Awfully dismissive. Well, ok, you won't have to write it but someone will. And those someone are going to curse whoever wrote that abomination of a spec.
A spec that: - That doesn't respect backwards compatibility - Looks like pure torture to write in - Misunderstands some part like OpRem
I'm not very confident in it to be honest. Looks to me just another overly elaborate moat for browser implementors.
https://github.com/gpuweb/gpuweb/issues/566
Basically. Rather than doing something better w3c is designing by committee so hard it somehow made worse OpenGL.
A fellow contributor, that had to deal with pain of OpenGL, laughed this shit out of the gate.
And I mean look at it. Who in their right mind looked at that and said, yeah that looks decent.