The challenges and benefits of a functional reactive frontend
summary
Claims that a frontend built with ClojureScript with core.async and Om (React) centralizes a single app state and makes UIs purely functional are supported by concrete choices and outcomes: cursors to scope state, virtual DOM diffs to avoid extra DOM work, a paginated feed implemented end to end, measured 2–4× faster TodoMVC-ish performance, and a codebase reduction from ~26,000 to ~5,000 lines. It runs in production at Prismatic with faster iteration but requires a mental shift and smaller ecosystem tradeoffs.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:59Talk outline
- 14:43Urban Exploration
- 16:05MVC frameworks are complex
- 17:28React Component
- 21:30:feed :title "Story 1"
- 32:54A Prismatic
related talks
27mThe Functional Final Frontier
29mDesign decisions in React-based ClojureScript applications
30mBuilding CircleCI's Front end With Om
35mClojureScript & User Interfaces: Simplicity yields Possibilities
40mFunctional Client-Side ClojureScript UI Programming with Webfui
43mEvolution of Functional UI Paradigms
38mThe Front End Architecture Revolution
40mReactive Programming: A Better Way To Write Frontend Applications