Elm, Is It as Good as They Say?
summary
Elm used in production for a year largely delivers on its claims: no runtime errors for normal code, clear compiler messages, and far fewer runtime user bugs. Trade-offs include more verbose code and many type signatures, long incremental build times (20+ seconds) that slow iteration, and risky JavaScript native interop which caused the few production failures; the team ships client and server apps, writes fewer unit tests, and sees stable deployed services after initial integration costs.
AI-written summary · about
chapters (16)
- 0:00Elm intro
- 1:30Elm language
- 5:03Syntax to JS
- 8:09Strong types and errors
- 12:47Custom and generic types
- 16:23Immutability and state
- 19:10Effects and side effects
- 21:59Elm architecture
- 26:06Virtual DOM rendering
- 26:48Async tasks
- 31:02Production feedback
- 34:12Pros and cons
- 36:57Verbosity and learning
- 39:25Community and evolution
- 41:54Performance and use cases
- 43:42Q&A
related talks
48mHighway to Elm!
50mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
26mElm - Frontend with Guarantees
16mElm as an antidote to front-end fatigue
33mElm and React in production
15mPutting the fun in functional with Elm
30mElm the Game Changer
47mElm or how I learned to love front end development