IMHO. Maybe I overexaggerate. Anyway, the author, from my perspective has decided that clojure IS in fact for him, but clojure on the JVM is not, so he chooses to use a different one.
IMHO. Maybe I overexaggerate. Anyway, the author, from my perspective has decided that clojure IS in fact for him, but clojure on the JVM is not, so he chooses to use a different one.
I've been told this a couple times. I doubt I'd thrive in that world though, unless I was selling something I actually gave a damn about.
IDK, is guile a scheme? guile is it's own thing, but it's definitely a scheme. What about racket? Racket has a whole bunch of stuff that mit-scheme doesn't. But it's still kind of in the scheme family. That's the parallel I was drawing. That and the statement that Hickey made in his History of Clojure that Clojurescript _was_ clojure, not some kind of spinoff.
I'm certainly not detracting from Janet and Fennel, but they _are_ quite close to clojure proper. There is a clear lineage.
I would generalize your observation as a logical consequence of Greenspun's tenth rule and conclude that we will eventually get a hosted lisp for any sufficiently relevant programing language.
However, the broader lisp community writes code very differently from typical clojure. Different idioms, slight syntax variations, completely different tooling and ecosystems.
While I can agree with you that for 'us' it certainly feels emotionally true. But if you go into other lisps scheme, racket etc you would notice huge differences. Differences which may feel even stronger than java vs c++ diff.