I mean, recently I saw Clojure for . Net and Clojure without JVM (forgot the name). If you don't need/want JVM, then why would you use Clojure over e.g. Common Lisp?
Clojure is a lisp-1 which, surprisingly, feels better to use than a lisp-2. Much more intuitive. (You can kind of also have a function call returning a function in the first position of a list and it just works. Common Lisp doesn’t like that at all and you need funcall or apply.)
The immutable data structures and better array and hashmap syntax and ergonomic hashmap argument destructuring remove a lot of mental overhead. Kind of like Python or JSON-in-Javascript.
Having slight syntax variation like square brackets for let bindings and one less level of nesting in let bindings makes it easier to read. Still homoiconic, though. So you get the best of both worlds.
The hygenic macros helped me design better anaphoric macros.
EDIT: typo
Hylang also had a good take on anaphoric macros in relation to threading macros. Clojure makes it more obvious that explicitly passing in the anaphoric symbol at the call-site is better for maintainability. This offers threading with arbitrary argument positions instead of forcing first or last position.
Clojure transducers finally broke the ice on common lisp series. The CL side of this is horrifying. SBCL seems to have dropped its sb-series contrib module. But it moved us far enough along that we now have parenscript-series. So upside all around.
Don’t know enough Fennel (Lua) or Elixir (Erlang) yet, to have any useful comments there.
Clojure makes stronger choices about the default style: immutable data, transformations over collections, and explicit tools for managing changing state.
Zooming out you're right: it's lisp and jvm is a difference. Zooming in and there are different ergonomics and incentives on how to structure the program.