I have come to the conclusion that all PLs are VPLs. The first VPL I learned was assembler. Pond'ring aloud, thoughts welcome... Background: Inspired by the post by @Duncan Cragg, I started to categorize VPLs. I think that I'm up to 9 simple variants. The main knobs that can be turned for PL design seem to be: (1) syntax affected by visualization technology, e.g. 1960s grids of non-overlapping pixmaps called "characters" vs. more modern raster graphics and vector graphics, (2) semantics of control-flow, e.g. 1960s sequentialism implied by line-by-line reading of code and blocking function calls vs. 1970s control-flow isolation like UNIX processes vs. more modern closures (effectively invented in the 1950s :-)). [FTR, assembler is position-based, using crude graphical grids of columns and rows, whereas C is not position-based, using simple eye-candy indentation for human (vs. machine) readability].

Cross-ref: https://futureofcoding.slack.com/archives/CEXED56UR/p1743107314652809?thread_ts=1743080787.860049&cid=CEXED56UR 🤗