Who Cares Why Undefined Is Not a Function
summary
A Netflix-like single-page app uses React, reactive streams, Backbone and a black-box video player and ends up with inconsistent state, unsubscribed streams, and many slip-of-the-hand runtime errors culminating in a message like undefined is not a function; switching core modules to Elm produces a statically typed, pure-functional codebase that catches typos and missing cases at compile time, lets a production system of 100,000+ lines run with far fewer runtime crashes, and forces clearer APIs so fewer developers burn out.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:22JavaScript struggles
- 4:44Unmaintainable code consequences
- 5:46Elm as solution
- 7:14Elm catches errors early
- 10:10Elm in large apps
- 12:23Elm vs JavaScript
- 13:53Conclusion
related talks
34mReact Is Hard but Not for the Reasons You Think
23mGetting rid of runtime errors with Elm
35mBack to React
28mHow to use Functional Programming in your React app
01h 28mFunctional Programming for the Web with Elm
37mReact is hard but not why you may think
38mThe challenges and benefits of a functional reactive frontend
51mElm-Friendly Functional Programming For The Web