The gigantism of Reatom
summary
Explains what features and patterns can fit into a 2KB library and how to build applications of any complexity on top of it, using the Reatom state manager as the concrete example. Describes how choosing the right abstractions can drastically reduce code size and complexity, and extracts general principles applicable to any codebase.
AI-written summary · about
chapters (11)
- 0:00Welcome to Reatom
- 3:34What is Reatom
- 7:27Motivation and history
- 16:00Redux problems vs Reatom
- 23:18Transactions and rollbacks
- 29:26Inversion of Control patterns
- 36:12Data normalization
- 40:27Migrating from Reatom v1
- 44:39Reatom ecosystem
- 52:10Usage examples
- 55:40Q&A
related talks
23mReactive Programming Made Simple
37mRethinking reactivity
31mThe World Beyond Components
52mState management beyond the libraries
29mDesigning very large JavaScript applications
20mBreaking Down Modularization
46mBuilding Reusable Components ... That Are Actually Reusable
32mWhy Invent a Framework and How to Live with It?