Simplifying Web App Development With Elm and Functional Programming
summary
Argues Elm and functional programming reduce developer overhead by trading many small choices for one opinionated path, claiming no runtime errors from static types and compiler checks and showing how union types model AJAX as a remote data union type so the compiler enforces exhaustive handling. Describes elm-format and the package manager that enforces semver and public docs, then builds an in-app component gallery by exporting Elm docs as JSON and rendering live previews inside the app; team of 15 with limited FP experience adopts it and sees faster, safer development.
AI-written summary · about
chapters (13)
- 0:00Simplifying Web App Development With Elm and Functional Programming
- 1:14Choosing the tools that work for you
- 2:27Tools don't lapse in discipline, but people do - Charlie Koster - @ckoster22/elm-models-as-types-d913002b58fb
- 4:38Simplicity
- 15:16Goal: make great user experiences
- 18:05Remote data
- 24:05Rethinking the problem
- 27:55Third-party packages
- 32:26Documentation
- 41:16Implementing previews Values are identified by Imodule name value name
- 43:16Reducing mental overhead
- 45:08Developer happiness
- 51:55Thank you
related talks
39mDeveloper Happiness on the Front End with Elm
51mElm-Friendly Functional Programming For The Web
47mElm or how I learned to love front end development
01h 28mFunctional Programming for the Web with Elm
41mWriting Reliable Web Apps With Elm
38mConfident Frontend with Elm
50mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
31mMake the Back-End Team Jealous: Elm in Production