3 ms·
I would build around a constrained high-level concept. Something like actors, perhaps. It would be assembly-like, command-oriented. I would then build a visual
by pfraze 5y ago
I would build around a constrained high-level concept. Something like actors, perhaps. It would be assembly-like, command-oriented.
I would then build a visualization environment which shows what the actors are doing, possibly step-by-step. It would show them moving values between registers and buffers. It would show messages passing between actors. It would show new actors create and finished actors die and errors get dumped into the canvas.
Your concept as an end-user would be that you're programming these automatons. You could clearly visualize what's occurring and debug control-flow or algorithmic issues by stepping through their movements.
Maybe not a great idea in the long run, but if it was a weekend lang jam, that's what I'd do.
- abecedarius 5y agoYou might like https://en.wikipedia.org/wiki/ToonTalk https://en.wikipedia.org/wiki/ToonTalk