Enemy of the State
summary
Argues that route handlers must stop driving state transitions and instead emit events that a dispatcher handles, showing a concrete pattern implemented with Backbone views, a dispatcher, and a layout composer and referencing Chaplin.js and Marionette region ideas; demos include a list/remove “party animals” flow refactored so views mutate their own models and remove themselves, while the router only observes URL changes and raises module-load events, yielding clearer encapsulation and manageable module lifecycles.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:23PRESENTATION
- 7:27How do we TRANSITION STATE?
- 7:37ADDRESS STATE AND EVENTS
- 14:11ROWS IN A DATABASE
- 15:03SHOE HORNED
related talks
25mEnemy of the State
41mManaging State in Angular Applications
33mPitfalls and Opportunities of Single Page Applications
27mOn the Development of Reactive Systems with Ember.js
30mThe SAM Pattern: a distributed system view of Front-End architectures
22mN Things You Didn’t Know About the Router
28mStop Breaking the Web
58mFrontin' like a Back-er