Reposted by Iwo Plaza | TypeGPU
JavaScript can do almost anything… but operator overloading is still missing. 👀
At What The Stack 2026, @iwoplaza.dev from Software Mansion will talk about the weird, clever, and sometimes cursed ways developers have tried to solve it, including the approach TypeGPU uses today. ⚡🧠
![// Zod-like schema for I/O with the GPU
const Material = struct({
albedo: vec3f,
});
// Allows `material` to point to different memory on each draw-call.
const layout = tgpu.bindGroupLayout({
material: { uniform: Material },
});
// A typed reference to the eventually bound resource.
const { material } = layout.bound;
// ^? TgpuBufferUniform<WgslStruct{ albedo: Vec3f }>
// Constant at shader creation time, precomputed.
const sunDir = normalize(vec3f(-0.5, 2, -0.5));
// 🚀: `computeColor` is a function that can run on the GPU!
const computeColor = tgpu.fn([vec3f], vec4f).does((normal) => {
const diffuse = vec3f(1, 0.9, 0.7);
const ambient = vec3f(0.1, 0.15, 0.2);
const att = max(0, dot(normalize(normal), sunDir));
// 🎉: The type of `albedo` is infered, and properly type checked.
const albedo = material.value.albedo; // => v3f
const lightColor = add(ambient, mul(att, diffuse));
const surfaceColor = mul(lightColor, albedo);
return vec4f(surfaceColor.xyz, 1);
});](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:cjdlrryzvstnsci6u2gycm6o/bafkreia2k5itjcr4pjg374mn5xhvr4i25u4sjyvbza4ahf7w7epgqti6zi)
