ShaderToy as an ASIC Simulator Path
June 23, 2023

Browser/GPU noteOriginally posted 2023-06-23; rewritten here around GLSL as an inspectable simulation surface.

Included: ShaderToy, signed-distance fields, GLSL, visual circuit simulation, GPGPU-style kernels, and why browser-native computation was useful for fabric experiments.

Why GLSL Was Useful

ShaderToy and browser GLSL made it possible to put a small computation on screen quickly: a fragment shader runs many pixels in parallel, updates a visual field, and keeps the program close to the image it produces.

For fabric and circuit experiments, that matters. A shader can render local rules, routing, tile state, signed-distance-field geometry, and update behavior without first building a full native simulator UI.

Simulation Surface, Not Replacement HDL

GLSL is not Verilog. It does not replace synthesis, timing closure, placement, routing, or hardware verification. It is useful earlier in the path, where the goal is to explore a spatial rule, draw the structure, and see whether the local behavior reads correctly.

That is the ASIC-simulator connection in this note: browser/GPU code can carry visual and parallel structure while the idea is still being shaped.

Useful Scope

The useful result is practical: SDFs and fragment shaders give a compact way to prototype circuit-like visual systems, fabric renderers, and GPU-parallel experiments that can be shared as web pages.