Make the Back-End Team Jealous: Elm in Production
summary
A production web app originally built with React.js and legacy jQuery gets Elm introduced incrementally by replaced one Flux store via ports, preserving existing JS while isolating guarantees. The Elm compiler catches nearly all runtime exceptions at build time and the package manager enforces semantic versioning for every package, yielding far fewer bugs, much faster iteration (months cut to weeks), a working sentence‑rearrange UI for teaching active vs passive voice, and developers refactoring about three times as often.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 3:12React and Flux
- 6:15The First Version
- 9:15Why Elm
- 11:29Semantic Versioning
- 16:49Building a Live Validated Form
- 17:17Immutable Data Stateless Functions
- 18:57Tasks
- 19:59HTTP GET String
- 21:55Global Functions
- 22:18Missed Cases
- 22:48Life in Elm
- 23:54Retrospective
- 24:28Why didnt I
- 24:49Is it worth it
- 25:45Tina Fey quote
- 26:01Elm port system
- 27:58Introducing Elm to a JS web app
- 28:19Is Elm worth it
- 28:36Improvements
- 30:40Reliability
related talks
47mElm or how I learned to love front end development
41mWriting Reliable Web Apps With Elm
26mElm - Frontend with Guarantees
24mElm — new language, new you
54mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
01h 28mFunctional Programming for the Web with Elm
28mConvergent Evolution
39mDeveloper Happiness on the Front End with Elm