> Talk is only 25 minutes, and most of the public probably didn't use Clojure before. you kinda answered your own question 🙂

maybe you can briefly show code as a sign of its concision. but even that can be misunderstood / not understood at all

Yes, kind of, it's less Clojure on each iteration, if telling it's a lisp, and it can run on the JVM and also compile to js seems not relevant. But if there are question during demo I might show some code.

Agree with vemv. I did that and failed. If you show too much code, then the ideas get lost. I recommend talking only about the ideas and maybe some curiosity-inducing statements/questions like What if you could write a babel transform just as easily as a function, and the language supported it directly?

Maybe ease fears about bundle sizes "ClojureScript for Skeptics" style, by showing an example through advanced compilation.

if it adds to your point then do as much as it’s useful. otherwise, maybe plug it and say to ask me about it after the talk 🙂