I would call it an exolisp. Its very pointed use case is to enhance Python with better metaprogramming facilities. It's often compared to Clojure, but Hy's own

I would call it an exolisp. Its very pointed use case is to enhance Python with better metaprogramming facilities. It's often compared to Clojure, but Hy's own documentation often uses Clojure as a contrasting example that reinforces this perspective. Clojure is built on top of Java, but the integration is somewhat loose in that Java semantics don't always map cleanly to Clojure semantics. Hy, on the other hand, deliberately stays very, very close to Python's semantics, even when that means making significant departures from how things are typically done in a lisp.