Clojure newcomer here, but here's the thought that's frontmost in my mind about ClojureScript...
I'm used to Clojure as a language that's solidly spot-welded to the JVM and the Java libraries. Just as "[1 2 3]" is legal portable Clojure code, so is "(.start (Thread. #(...)))" despite it being a blatant set of calls into Java, and so are the various Java-leaning reflection features. I think ClojureScript is a great piece of work, but I'm not sure what this means for language standardisation or portability. Is it still "real" Clojure? Clearly I can write programs, or distribute libraries, which run on one but not the other. Similarly, I'm sure there are common chunks of functionality (although I'm not enough of a JS programmer to suggest any) which are pretty crucial to some programs written in either Clojure but implemented differently. ClojureScript is still missing key parts of Clojure (e.g. agents) making even non- Java-ish programs non(-yet)-portable. I guess I'm interested in the road map, if any: are things heading towards some kind of common "ClojureCore" specification with ClojureJava and ClojureScript both supersets of this? What are the ramifications for library distribution? Or are "Clojure Classic" and ClojureScript different systems for different environments? In which case, what mileage is there in identifying and specifying the overlapping and identical areas and transparently developing for both? Sorry if the questions are stupid... I'm looking forward to having a good solid session with ClojureScript in a browser near me soon. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
