> I don't see a point in having very similar, but not 100% compatible languages on backend and frontend.
I have an applications consisting of frontend cljs code, backend clj code and some code that will be compiled to both ends (called cljc). Even if its not 100% compatible, I think its helpful that I only have to write data validation (e.g. clojure.spec) once and can use it in every part of the system. Also if you wrote pure algorithms for complex data structures, its nice to use it in cljs and clj. The parts that are missing to 100%, can often be bypassed with a simple reader conditional (https://clojure.org/guides/reader_conditionals).
> Some time ago (a year or two, I think?) CLJS got bootstrapped - is it finally possible (and practical) to use with node only?
I dont have much experience with this, but I think that shadow-cljs (http://shadow-cljs.org/) will make this mostly possible.
I have an applications consisting of frontend cljs code, backend clj code and some code that will be compiled to both ends (called cljc). Even if its not 100% compatible, I think its helpful that I only have to write data validation (e.g. clojure.spec) once and can use it in every part of the system. Also if you wrote pure algorithms for complex data structures, its nice to use it in cljs and clj. The parts that are missing to 100%, can often be bypassed with a simple reader conditional (https://clojure.org/guides/reader_conditionals).
> Some time ago (a year or two, I think?) CLJS got bootstrapped - is it finally possible (and practical) to use with node only?
I dont have much experience with this, but I think that shadow-cljs (http://shadow-cljs.org/) will make this mostly possible.