The document discusses ClojureScript, an alternative to JavaScript that compiles to JavaScript. It provides information on where ClojureScript can run, companies that use it, and benefits like structural sharing, core.async for concurrency, and immutability. It also mentions Google Closure Compiler and Library for optimizations and code splitting in JavaScript projects.

1. ClojureScript
Yet another flavor of JavaScript?

2. What’s wrong with JS?

3. Broken piece of shit?

4. Lots of stuff to worry about

5. Babel setup page

6. Babel setup page 2016

8. How to make the best
of JS?

9. Solar System of JS
http://shaunlebron.github.io/solar-system-of-js/#0

11. What’s Google
Closure?

12. Google Closure
• Closure Compiler
• Closure Library

13. Closure Compiler
• Dead code elimination
• Code splitting
• Optimizations
• Cross-browser compatibility

14. Closure Library
• Data Structures
• Namespaces
• Dependency Management
• Event Handling
• (RTFM)

15. Is ClojureScript worth
it?

16. Where can you run it?
• Rhino
• Nashorn
• Node.js
• JavaScriptCore
• Web Browsers (starting IE6)

17. Who uses?
• Consumer Reports
• eBay
• Prismatic
• Reuters
• CircleCI (https://youtu.be/5yHFTN-_mOo)

18. Benefits
• Structural Sharing
• core.async (Go style channels, 10,000 Processes
Example, 100000 DOM updates)
• Immutability for efficiency (Facebook rolled
Immutable.js)
• Implicit dependencies (Closure Compiler)

19. • PayPal article on Node.js and JS combination
• Lots of what Clojure provides (i.e. Prismatic
Schema)

20. Dependencies
Dependencies WIKI

21. Code splitting

22. JS interop