Ember Data and the Way Forward
summary
Ember Data is refreshed and refocused: adapters and serializers are rewritten to normalize input, promises replace bespoke async plumbing, and promise-aware relationships make every relationship access return a promise so lazy and remote data behave consistently. The store implements an identity-map caching so the same type/id yields the same object. Work concentrates on the locality problem of pushed or out‑of‑order payloads and the result is a slimmer, more reliable Ember Data approaching 1.0.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:18Programming without fluent English
- 7:59Frameworks for problem-solving
- 10:50Ember Data’s evolution and features
- 16:51Data transformation in Ember Data
- 20:26Asynchronicity and promises
- 26:09Caching and identity maps
- 28:13Combining data features challenge
- 31:42Future directions and 1.0 focus
- 33:23Q&A
