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.
> Correct me if I'm wrong, but was your stance that there were no immediate plans to implement features such as protocols in Jank?
Protocols, records, and Clojure structs will definitely be a part of jank. They have been lower priority than improving some of the more commonly used Clojure features, smoothing out the C++ interop edges, and providing excellent tooling. Still, I have been working toward supporting them already. jank will have them before its production release.
> 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.
Yes, this is a neat approach. Making dialects maximally portable across existing Clojure JVM code is compelling and I think jolt's momentum, due to your usage of AI, has allowed you to pioneer an approach here faster than other dialects have done. In the coming couple of years, I can see us arriving at a more wide-spread approach of registering these shims so that the large corpus of Clojure JVM code can be used in various dialects without requiring library authors to add reader conditionals everywhere.
However, "Clojure" these days doesn't only mean Clojure JVM. We don't yet have a specification for Clojure, but reasonably the intersection of Clojure JVM, ClojureScript, and ClojureCLR is the target compatibility point for most dialects. For example, ClojureScript doesn't have JVM interop, emulated or otherwise. But nobody would ever say that ClojureScript is not Clojure. I discussed this exact point in my Conj talk this year, since there seems to be some outdated reasoning that "Clojure" means Clojure JVM. It does not.
> 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.
Yep, I understand this philosophy. I can appreciate it. The reason why I bring up disclosure is because you and I both know that this is divisive. There are people who will see jolt as a front-runner, due to its AI usage, and there are people who would rather abstain or at least wait until the dust settles. Providing people the necessary information on the label so that they can make this decision themselves is the respectful, transparent thing to do. I need to do better here as well and I have already publicly stated I will update the jank repo and website with clear disclosures for how I have used AI, which is mainly for troubleshooting and bug fixes. This will be coming with the beta release.