On Fri, Jan 9, 2015 at 1:55 PM, gvim <[email protected]> wrote: > I have 3 questions regarding Clojurescript on NodeJS: > > 1. Optimisation > Is optimisation relevant for NodeJS deployment? Many of the benefits of > cljs optimisation seem to be related to JS in the browser. There are 2 > scenarios here - NodeJS modules used within a project setup with Leiningen > and a project setup with a NodeJS framework (eg. sails) to which > Clojurescript has been added. >
Advanced optimizations are less important. Only concatenation and `:static-fns true` really matters. Even this is less important outside of high performance code you might write yourself, the standard library is always compiled with `:static-fns true`. > 2. Callback hell > Does Clojurescript help to alleviate NodeJS callback hell or just sweeten > the syntax? > Yes see core.async. > 3. Mutable state > If we end up doing a lot state mutation in NodeJS with: > > (. setValue someObject "value") > > .... at what point does it defeat the purpose of using Clojurescript? In > other words, what value can Clojurescript still add to predominantly JS > code? > The same could be said of Clojure & Java. There is still much value to be derived. HTH, David -- 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.
