Resources^2 / Resources on Resources
summary
Claims that resources unify reactivity by representing a value bound to a lifetime and replace awkward effects with composable functions. Demonstrates working examples: a clock interval with co‑located cleanup, a socket-powered “last visitor” updater, cancelable fetch resources for parallel endpoints, modifier animations, and app‑scoped state that behaves like a service. Uses Ember resources today, shows how it maps to Starbeam and the use composition API, and the demos run live in the Rebel playground.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:44Talk goals
- 5:54Ember Octane reactivity
- 8:24Values cells and resources
- 10:31Resource implementation
- 12:17Resource lifetimes
- 14:45Why resources matter
- 16:31Old patterns vs resources
- 18:38WebSocket resources
- 20:01Data fetching resources
- 21:47Loading data outside routes
- 23:13Resources for modifiers
- 23:56Resources as services
- 25:43Resources vs components
- 27:08Components as wrappers
- 28:11Starbeam future
- 28:55Next steps
- 29:17Key takeaways and closing thoughts
related talks
01h 02mStarbeam: Universal Reactivity And What It Means For You
31mThe World Beyond Components
28mExploring Angular's Resource API
29mThe World Beyond Components
28mHandling Legacy APIs with Domain Driven Design and Reactivity
23mReactive Programming Made Simple
37mRethinking reactivity
19mSolidJS: Reactivity Unchained