Related, a self destroying game I built some time ago: https://void4.github.io/ The yellow dot is the instruction pointer, the red dots represent the program memory. If you hit the ball just right you can introduce graphic glitches. Most times, the instruction pointer gets out of bounds however.
That's kinna like the story about the guys who coded a Tron lightcycle game on the Apple II. Failure to properly bounds-check the lightcycle position meant that the cycles could be driven off screen, corrupting main memory and the game code itself -- much like what happened in the move Tron.
One thing I've often wanted to do, but didn't have the time to, was to take Turing Drawings: https://github.com/maximecb/Turing-Drawings ( faster asm.js variant here: https://github.com/darius/Turing-Drawings ), which runs a random Turing machine to generate abstract art and put the machine description in the image itself, so it could self-modify.
I was looking through the source and learned that Python's modulo operator is based on floor-division (rather than round-toward-0 division like in C). In case anyone cares how Python actually does in in C, for small ints its defined at https://github.com/python/cpython/blob/master/Objects/longob...
This is really cool and I'd love to play with it, but my eyesight isn't good enough to hit the ball more than once at a time. Is there anyway you could post an upscaled version?
