@clementd ahh the flow direction is the direction for reading the program? I didn’t get that
@immae yes, execution starts top left, going right, and then commands are read one at a time. Some commands manipulate the stack, some alter the pointer direction. Some output SVG elements. All combined, it's a convoluted way to generate SVGs. The perlin inputs provide a way to configure a noise generator, which is more suitable than pure randomness for fancy results.
@immae the program space is a torus: when reaching an edge, the pointer starts over on the other side.
@clementd yes the stack part and the torus I got it (first things I "tested" 😁), I just wrote it linear as any sane programmer would do 😛
@immae so it's both bona fide stack-based fun, plus a twisted graphical execution model
@immae it generates SVG by running programs written in a stack-based language with a fun execution model: the execution pointer moves over a 2d map of instructions: the program itself