Elm — new language, new you
summary
Company migrates a 50k‑line AngularJS app to Elm and reports completing the rewrite within a year, using Elm’s Model‑Msg‑Update architecture, ports for interop and webpack integration. Static types catch many errors at compile time, fuzz testing exposes edge cases, and unit tests run fast. Benchmarks show Elm rendering a Todo list a few percent faster than React and much faster than old Angular 1.x; smallest bundles are about 8KB hello bundle. Tradeoffs: steep learning curve and scarcity of Elm devs despite productivity gains. rewrote 50k LoC in one year fuzz testing finds edge cases
AI-written summary · about
chapters (11)
- 0:00Introduction and motivation
- 3:37Why choose Elm
- 5:07Elm basics and features
- 8:59Performance and Redux comparison
- 10:00Type system benefits
- 12:15Elm syntax and learning curve
- 15:29Operators and functional style
- 16:35Ports and integration
- 17:20Testing and debugging
- 19:06Building a simple app
- 21:11Review and summary
related talks
31mMake the Back-End Team Jealous: Elm in Production
54mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
26mElm - Frontend with Guarantees
16mElm as an antidote to front-end fatigue
47mElm or how I learned to love front end development
41mWriting Reliable Web Apps With Elm
50mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
01h 28mFunctional Programming for the Web with Elm