Confident Frontend with Elm
summary
Explains how Elm replaces mutable JavaScript patterns with pure functions, immutable records and union types, and implements a counter and a GitHub-fetch example that actually runs and returns data via commands. Shows how maybe forces handling of absent values and how the compiler catches typos and shape errors. Claims real teams run large Elm codebases — 36,000 lines with no runtime errors reported — and emphasizes the explicit update/view/model flow that makes core logic testable.
AI-written summary · about
chapters (16)
- 0:00Start
- 8:11Reducers
- 8:59Data Flow
- 9:39Recommended Reading
- 12:51Pipes
- 13:55Type Annotations
- 14:24Union Types
- 16:00Type Aliases
- 18:26The Null Reference
- 21:45Tasks
- 23:36The Elm Architecture
- 24:30Hello World
- 28:08Initial Model
- 31:03Elm Ecosystem
- 31:58When Should You Consider Using Elm
- 35:54Can You Render Elm Server-Side How Do You Deal with Seo
related talks
39mDeveloper Happiness on the Front End with Elm
54mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
41mWriting Reliable Web Apps With Elm
50mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
47mElm or how I learned to love front end development
31mMake the Back-End Team Jealous: Elm in Production
56mSimplifying Web App Development With Elm and Functional Programming
26mElm - Frontend with Guarantees
