anchor.diff:  
   Running a Node.js REPL is similar to running a browser REPL. In order to specify
   a REPL which uses a different JavaScript evaluation environment you supply
  -`--repl-env` or `-re` for short. This value defaults to the browser REPL but in
  +`--repl-env`. This value defaults to the browser REPL but in
   this case we want to specify `node`.
   
   [source,bash]
   ----
  -clj -m cljs.main -re node
  -----
  -
  -On Windows:
  -
  -[source,bash]
  -----
  -java -cp "cljs.jar;src" -m cljs.main -re node
  +clj -m cljs.main --repl-env node
  +----
  +
  +On Windows:
  +
  +[source,bash]
  +----
  +java -cp "cljs.jar;src" -m cljs.main --repl-env node
   ----
   
   All the previously described REPL interactions for the browser should
  
positive.code: 
  [source,bash]
  ----
  clj -m cljs.main -c hello-world.core -r
  ----
  
  On Windows:
  
  [source,bash]
  ----
  java -cp "cljs.jar;src" -m cljs.main -c hello-world.core -r
  ----
  
  Your default web browser will open to a page that looks like the following:
  
negative.code: (println "Hello world!")
  ----
  
  We can create a release build by setting the appropriate value for the
  `--optimizations` flag. The default optimization level is `none`, but this time
  we want to use all the optimizations provided by both ClojureScript and Google
  Closure Compiler - this can be done by specifying `advanced`. Other valid
  options for `-O` are `whitespace` and `simple` but these are less commonly used:
  
  [source,clojure]
  ----
  clj -m cljs.main --optimizations advanced -c hello-world.core
  ----
  
  On Windows:
  
  [source,bash]
  ----
  java -cp "cljs.jar;src" -m cljs.main --optimizations advanced -c hello-world.core
  ----
  
  This process will take significantly longer which is why we don't use
  