Olympus

And see also: the Olympus language (https://github.com/rottytooth/Olympus). It explicitly builds on INTERCAL, and reverses the power dynamic -- we pray to the gods and offer them praise so that our code will run

Yes, you build a command in pieces, breaking it down so as not to seem too petty to the gods in any single line of code. The longer the request, the more praise must be given, but also you can’t repeat yourself too much (if you call Ariadne “mistress of the labyrinth” the first time, the second time you might instead call her “wise and cunning one whose agile mind finds purchase on the frailest of notions.” The project is here: https://github.com/rottytooth/Olympus and here’s an introduction: https://www.youtube.com/watch?v=Agq99SyHfFw

I’m finishing several esolangs for the first artist’s monograph of programming languages, out in Sept: https://mitpress.mit.edu/9780262553087/forty-four-esolangs/ including a hands-free (and not dictated) language. I recently completed Valence: a language with polysemantic programs https://danieltemkin.com/Esolangs/Valence on GitHub: https://github.com/rottytooth/Valence Older work includes Folders: code written as a pattern of folders: https://github.com/rottytooth/Folders , Entropy: where data decays each time it’s read from or written to: http://entropy-lang.org/ and Olympus: where code is written as prayer to Greek gods, who may or may not carry out your wishes: https://github.com/rottytooth/Olympus (a way to reverse the power structure of code, among other things). I have three more to complete in the next few months.