anchor.diff:  java -cp "cljs.jar;src" -m cljs.main -s
   ----
   
  -`-s` is for `--serve`. This command does not start REPL, so a browser window will not be automatically
  -opened. Navigate to http://localhost:9000 using your favorite browser. Check the
  -JavaScript Console, you should see `Hello world!` printed. The build in web
  -server gzips JavaScript. Check your browser network tab and you should be able
  -to confirm that the total JavaScript payload is now around 20K.
  +`-s` is for `--serve`. This command does not start REPL, so a browser window
  +will not be automatically opened. Navigate to http://localhost:9000 using your
  +favorite browser. Check the JavaScript Console, you should see `Hello world!`
  +printed. The builtin web server gzips JavaScript. Check your browser's
  +JavaScript Console Network tab and you should be able to confirm that the total
  +JavaScript payload is now around 20K.
   
   [[running-clojurescript-on-node.js]]
   == Running ClojureScript on Node.js
  
positive.code: ----
  
  Let's build your Node project. We can specify that we want to generate code for
  a specific JavaScript target via `-t` for `--target`. `-t` defaults to browser.
  Other valid but less common options are `nashorn` and `rhino`. We're also using
  `-o` for specifying the `--output-to` file:
  
  [source,bash]
  ----
  
negative.code: optimizations. While advanced optimizations does apply performance
  related optimizations, these are now largely obviated by optimizations
  present in modern JavaScript virtual machines like V8, SpiderMonkey, and
  JavaScriptCore. For Node.js, `simple` or `none` optimizations suffice.
  ====
  
  [[node.js-repl]]
  