nilaymaj

You're right, 5ms updates aren't really any more useful than 20ms updates. Although for the current esolangs `React.memo` serves most 5ms use-cases, I'll be happy to implement fixed-rate updates or debouncing when a visualizer gets too complex for simple optimizations.

Theoretically, the visualizer window can show anything I think - as long as the required props support structured cloning[0], it's really just a React component. Performance is the only limit, but the above methods will help when that limit is reached. A Leaflet.js map for the Taxi[1] esolang will be interesting to implement, for example.

[0] https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...

[1] https://bigzaphod.github.io/Taxi

I may have a bit of a soft spot for English-y esolangs :)

Yeah, LOLCODE should fit right in but Piet is tricky. I don't think a proper Piet editor can be added, but a possibility is to map each color to a relevant character and set up the right background colors for Piet in the editor - let me know if that makes sense in usability. Some added functionality for exporting as PNG may be required too.

Thanks a lot! And I agree, the docs button is more important than it is shown to be right now - working on it. (edit: done. the animation is somewhat powerpoint right now though)