I'm guessing you'd probably break the declarativeness if you exposed the full power of LISP, but limited subsets in YAML work pretty well. I especially like ho

I'm guessing you'd probably break the declarativeness if you exposed the full power of LISP, but limited subsets in YAML work pretty well. I especially like how well suited it is to visual block based editing. Blockly and Node Red let you put stuff anywhere in 2D space, a satisfying auto formatter isn't really possible, and traditional flow charts can easily get big and messy. But if you look at DRAKON, their charts pretty much always look nice. And looking at ladder logic, It's almost but not quite a set of 1D flow charts. If you strip it down more, events that trigger a list of commands until a command returns False is a really simple model without much learning time, and it's very easy to create a visual editor Giving people the full power of LISP would probably result in people writing imperative programs rather than building up an ecosystem of declarative plugins though. And it seems that the consensus is it doesn't become a LISP just because you can implement it in nested lists....