What?

Observations
- It’s very bad at tricker React state issues (stale vars in closures)
- It’s pretty bad at esoteric web APIs (audio)
- Cursor is low quality, very buggy, no support
- Claude code is probably better choice (more expensive)
- Still requires heavy human 🧠 and 🙌, can’t yolo projects

There is a secret 10x bonus if a pipe path ever connects from top to bottom or left to right. However I'm not sure if it's possible for the bonus to actually happen! The pipes usually rotate in alternating zigzags, not in a way that leads to long contiguous connections.

Fwiw shaderfrog is a code editor, you still write raw GLSL, you can see the source code by double clicking red or green nodes in the link above. Connecting nodes is like importing the other shader as a module, and inlining its main function. “Hybrid” graph and code editing

Shaders are inherently visual so I like the idea of some kind of shadercn library having preview images for everything, including functions.

Shader programs, conveniently, are easy to render with a main() fn. And shaderfrog turns full shaders into modules, so they are portable + composable.

Glslify (now dead) is another example- shader snippets published to npm.

@shaderfrog.com 2.0 is also meant to be that - every shader on the site is composable with any other shader. For example this is made up of a few smaller shaders shaderfrog.com/2/editor/clk...

It’s a webgl (browser) shader editor I created. That shader linked is in a three.js scene. But the editor can support any webgl engine. m.youtube.com/watch?v=8u61...

Also there are countless LLM options, but Google AI Studio lets you generate and use an API key immediately for prototyping aistudio.google.com/app/apikey