I am the author of jank. Saying that jank "does not aim to be a drop in replacement for Clojure" may send the message that jank is not a full Clojure dialect. This is unclear at best. jank is a native Clojure dialect with seamless C and C++ interop and a strong native ecosystem story, including native project and dependency management.
I believe what you're trying to say there, with "drop in replacement", is that jolt emulates common Java interop forms in Clojure JVM such that code written for Clojure JVM doesn't need to be ported to run on jolt. This a compelling feature which other dialects are tackling as well.
What I would mention as a key difference between jank and jolt, aside from the C++ story and native project management story, is that jolt is very much AI coded and jank is not. jolt doesn't disclose this on its website or Github readme, but it's something which clearly matters to a lot of people.
Fwiw, I’d like to see both succeed, while taking very different approaches.
Jeaye, you’ve been doing amazing work on jank over the years, please keep going!
It doesn't disclose but also doesn't hide it. Author obviously cares more about the product than about the ideology.
It feels superficially similar to the recent vibe-clones of unreleased games, competing with the original for attention purely on time to market, or even blackmailing the dev, demanding ransom to not release it...
I've been occasionally checking up on jank for a few years now, and thanks for resisting the temptation to go slop and doing things the proper way.
Correct me if I'm wrong, but I recall you mentioning that your stance is that there were no immediate plans to implement features such as protocols in Jank?
Jolt aims to faithfully implement the totality of features that current JVM Clojure implements along with shim for Java surface to facilitate existing code to run.
Meanwhile, I don't see the tooling used to develop the language as the key difference in the language itself. I understand this is important for some people, and that's fine. However, that has little to do with the language itself , its features, or its overall functionality. So, for me personally, that is not an interesting distinction. What matters to me is what I can use the language for, and what code it is able to run.
I'm looking forward to trying out jank!