Getting rid of runtime errors with Elm
summary
Elm claims it catches all runtime exceptions by using a strict static type system, pattern matching and pure functions; examples show partial application, function composition, and the Maybe type eliminating null checks. JSON decoders fail fast if fields are missing, HTTP calls become commands that return messages, and JavaScript interop happens through ports. Comparison to React+Redux highlights immutability, no direct DOM access, smaller curated libraries, missing server-side rendering and bundle-size concerns; one large codebase reports just a single runtime error.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:51PARTIAL APPLICATION IN JAVASCRIPT
- 3:58REVERSE AND REPEATA STRING
- 4:44FUNCTION COMPOSITION
- 5:29MOST BASIC UNION TYPE
- 6:22UNION TYPES WITH PAYLOAD
- 9:20IMMUTABILITY AND PURE FUNCTIONS
- 9:56WHAT COULD GO WRONG HERE?
- 12:48WHAT ABOUT SIDE EFFECTS?
- 15:53HOW DOES ELM INTEGRATE WITH JAVASCRIPT
related talks
54mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
39mDeveloper Happiness on the Front End with Elm
41mWriting Reliable Web Apps With Elm
01h 28mFunctional Programming for the Web with Elm
29mRethinking All Practices "Building Applications in Elm"
38mConfident Frontend with Elm
50mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
48mHighway to Elm!