> it solves the actual problem perfectly The whole post was about how that doesn't solve the problem perfectly - there is no way to interactively edit the outp

> it solves the actual problem perfectly The whole post was about how that doesn't solve the problem perfectly - there is no way to interactively edit the output. > by embracing LISP principles directly This could just as easily have been javascript+json or erlang+bert. There's no lisp magic. The core idea in the post was just finding a way for code to edit it's own constants so that I don't need a separate datastore. Eventually I couldn't get this working the way I wanted with clojure and I had to write a simple language from scratch to embed provenance in values - https://news.ycombinator.com/item?id=43303314 https://news.ycombinator.com/item?id=43303314.