On the Elm Track with NSB
summary
NSB moves its web platform into Elm and after one and a half years has 14 Elm applications and 60,000 lines of Elm code powering almost the entire ticket purchase flow. A single Elm seat‑picker replaces three native implementations, built by two interns and running 1.5 years with virtually no runtime errors. Reuse comes from a component library plus private libs managed via git‑subtree/ld‑install. Elm 0.19 cuts payloads ~75% and compiles faster (5s→1.5s) but challenges remain: dynamic‑height animations and URL handling require awkward workarounds.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 1:16Starting with Elm
- 3:08Consumer app success
- 4:13Scaling Elm adoption
- 6:23Production and libraries
- 7:48Component library
- 9:41Documentation and reuse
- 12:02Managing private packages
- 13:16Challenges and upgrades
- 15:35Compiler improvements
- 17:07Key takeaways
related talks
53mElm in production
24mElm — new language, new you
26mDeveloping with Elm in a large application
41mWriting Reliable Web Apps With Elm
31mMake the Back-End Team Jealous: Elm in Production
26mElm - Frontend with Guarantees
16mElm as an antidote to front-end fatigue
47mElm or how I learned to love front end development