The whole point is that it isn't like duck. The general evaluation rule with few special cases is broken, it is a whole bunch of special cases. Adding data-structures to a Lisp ruins it. It become a mess of a wired syntax, various comprehensions and unnecessary explicit conventions.

The beauty and elegance of a Lisp lies in that there is nothing to remove - a few selected ideas put together - and one common for code and data underlying list structure. This leads to a compact, readable code with relatively easily "maps to" machine code, because the memory is flat.

I don't care what Rich Hickey said. For me he is much better salesman, than engineer. He is very clever at selling, no doubt. But the whole Java scam is about clever selling of unnecessary complications from the very first days.

Moreover, those Lisp experts I have learned from didn't even mention Clojure.)