@Dennis Can you add feedback that the execution of your source code is complete? Currently this can be achieved by looking at the runtimes in the Debug panel but this is collapsed by default. Currently if I'm actively working on something it's difficult to determine the difference between two executions that have the same output. Did I disconnect from the internet? Did I introduce a syntax error (that only outputs in the debug panel)? etc
A potential idea would be to have a "Done!" message that pops up and then maybe fades away after a second
Or maybe just have the debug panel open by default
I know the run button turns into a gear while the code is running
but sometimes execution is very quick and it could be missed
@Dennis adding on to ^, it would be neat if the tab title changed to reflect completed execution. Maybe with a (*) like when you get pinged in an SE chat room.
@Pavel @Poke Something like that could fulfill both purposes, although I'm still not sure why the gear isn't enough while you're in the tab.
@Pavel The differences are minor: brainbool uses . while Boolfuck uses ;, brainbool uses big-endian bit order while Boolfuck uses little-endian, and Boolfuck mandates a doubly infinite tape.