2022: A year of freewheeling apps
6 comments
Inspired by @ltratt's https://tratt.net/laurie/blog/2023/compiled_and_interpreted_languages_two_ways_of_saying_tomato.html, I spent some time kicking the wheels on my code map based programming environment by building a BF interpreter. Next up: reproducing in Lua Laurence's results regarding the compiler-interpreter spectrum. Here's the "load screen" for my environment, showing a visual overview of the code I've written. A little app for drawing graphs https://git.sr.ht/~akkartik/snap.love I've wanted something like this for a long time. Intended for small graphs where laying things out by hand is not too painful, and it's nice that things don't move around every time I make a change, as happens with graphviz (https://graphviz.org). The file format is also amenable to git; no long lines, and adding new nodes or edges doesn't reorder unrelated nodes and edges. |
A map for code
In this video, I start up in quick succession:
* a simple test app
* the 'driver' programming environment showing the map for the app's code
* the 'meta-driver' programming environment showing the map for the driver's code
On initial load the driver (glitchily) zooms out over the whole codebase before zooming back in to the previous session.
https://codeberg.org/akkartik/driver.love
(Inspiration: early side-scrolling videogames that would often start a new level by panning across all of it.)
A map for code
In this video, I start up in quick succession:
* a simple test app
* the 'driver' programming environment showing the map for the app's code
* the 'meta-driver' programming environment showing the map for the driver's code
On initial load the driver (glitchily) zooms out over the whole codebase before zooming back in to the previous session.