Rethinking All Practices "Building Applications in Elm"

on YouTube ↗29m

" summary

Claims that Elm eliminates a whole class of runtime failures by design, showing the compiler catching missing branches and the maybe pattern instead of null and preventing side effects in functions. Compares Flow and JS tooling, cites bundle size growth (100 KB to 360 KB) and explains the Elm Architecture and Signals / FRP wired to a single model and update loop. Emphasizes immutable data and that the type system can’t be opted out of, and notes early production use and tooling gaps.

AI-written summary · about

" chapters (21)

1. 0:00Intro
2. 1:25Size of JavaScript Applications
3. 2:35Rethinking Best Practices
4. 4:55Runtime Errors
5. 6:10Tracking Errors
6. 7:39Flow
7. 8:47Errors
8. 9:23Code
9. 10:12Examples
10. 11:45Type System
11. 14:02Dijkstra Quote
12. 14:40Uber for Cats
13. 15:31React
14. 16:25Elm
15. 17:30Stateless Functions
16. 20:42Immutability
17. 22:25Communicating State
18. 23:39Updating State
19. 26:30Constraints
20. 28:12Main Thesis
21. 28:33Resources

" related talks

• 50mBeyond JavaScript Frameworks: Writing Reliable Web Apps With ElmErik Wendel · NDC Oslo 2017
• 38mConfident Frontend with ElmJack Franklin · Full Stack Fest 2016
• 54mBeyond JavaScript Frameworks: Writing Reliable Web Apps With ElmErik Wendel · NDC London 2018
• 23mGetting rid of runtime errors with ElmJānis Miezītis · FrontCon 2018
• 56mSimplifying Web App Development With Elm and Functional ProgrammingIngar Almklov · NDC London 2018
• 39mDeveloper Happiness on the Front End with ElmKevin Yank · RailsConf 2017
• 16mElm as an antidote to front-end fatigueFrancesco Orsenigo · Decompress AU 2016
• 31mMake the Back-End Team Jealous: Elm in ProductionRichard Feldman · Strange Loop 2015