> Java interop being idiomatic is the worst part of Clojure But Clojure today is not only on JVM - I use nbb, and sometimes Squint; I fooled around Clojure-Dar

> Java interop being idiomatic is the worst part of Clojure But Clojure today is not only on JVM - I use nbb, and sometimes Squint; I fooled around Clojure-Dart; You can even wrap some Elisp into Clojure today, although I have yet to find a practical use case for that - Elisp is very text-oriented, while every other Lisp is data-oriented, and I lately don't have any tasks for Emacs that require data-centric approach. I also write some Fennel - iirc it started by the same person who authored Janet. I'm an early adopter - at some point one of my projects held second most starred Fennel GitHub thing. I switch between Lisps with almost no mental overhead - for me, they all practically the same language, but the absence of Clojure's standard library functions is a bummer, I suppose that would be the same in Janet. Perhaps that's slightly bigger annoyance for me than the absence of the built-in pattern matching in Clojure. So, the decision to pick Fennel was always answerable with a single: "do I need to target Lua?" question. I'm not exactly sure what questions would answer "why I should grab Janet?". I was thinking of using it instead of babashka for some shell-scripty things, but bb turned out to be a bit more ergonomic. Although impractically memory hungry. And Jolt now being a new kid on the block throws another wrench into my [in]decision. I guess I won't really know unless I try. Thank you for humoring me and telling me about Janet2, I only hearing about it now.