A couple years into clj/cljs fandom, I'm still enthused about the potential of the language, both as a language and as a set of approaches to reasoning about software.
I think that Clojurescript in particular could be disruptive, because the world of Javascript development is so large and so . . . mutable, shall we say. However, there is this barrier: https://github.com/clojure/clojurescript/wiki/Quick-Start . Personally, I'm in the school of thought that says that we underestimate this barrier at our peril. I don't want to debate the merits of leiningen or anything (it's awesome). I just thought it might be interesting to enumerate the technical barriers to a "npm install clojurescript" experience, because I don't have a full grasp of what they are. - Dependency on Clojure for compilation => dependency on JVM - ? -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
