Production Ready ClojureScript: Tales from the Frontier
summary
Compares a Python+JS stack (17 classes, 56 functions, feature prototype in one month, production in three months) with a Clojure/ClojureScript stack (4 namespaces server, 8 total with CLJS, one week to prototype, production in one month) and shows consistently lower cyclomatic complexity—around an order of magnitude lower in role logic. Describes using EDN/reader-printer, Google Closure libs, Enfocus, Shoreleave, Jetty, CDN and Mailgun; advocates baking static HTML, serving closure data to clients, using protocols for adaptability, and warns about CLJS youth, fast releases, missing protocol impls and JS-level debugging.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:39MOTIVATION
- 6:08A TALE OF TWO SYSTEMS
- 8:14DEFECTS - COMPLEXITY
- 9:48GETTING STUNG
- 13:09VALIDATION
- 16:46NEW HORIZONS
- 22:51CODE ORGANIZATION
- 24:59PROTOCOLS
- 28:13WHEN IN DOUBT - SERVER
- 29:38THIS ISN'T JAVASCRIPT
- 31:18PRODUCTION CLOJURESCRIPT
related talks
33mA Tale of ClojureScript in Production
27mBuilding functional Front-ends with ClojureScript
55mClojure and ClojureScript Update
41mClojureScript for Skeptics
35mThrough the Looking Glass
24mUsing backend languages for frontends: Why ClojureScript is an awesome idea!
49mClojureScript: Fun and productive web development with next level tooling
39mTransforming Software Evolution: Lessons from 10 Years of Clojure in Production