On the Development of Reactive Systems with Ember.js
summary
Claims that modeling behavior as statecharts (based on the 1985 paper "On the Development of Reactive Systems") cuts complexity, implemented with the ember-statecharts add-on to interpret a JS object describing states, transitions and side effects. Builds a working rideshare proof-of-concept (map, geolocation, requesting, picked-up, payment) that handles non-user events like driver unavailability via sent events. Result is explicit, visual behavior models, smaller per-component state machines, and fewer ad-hoc action handlers.
AI-written summary · about
chapters (7)
- 0:00Introduction to challenges
- 5:58Academic solution found
- 12:10Rideshare app demo
- 19:13State chart benefits
- 21:18Implementation in Ember
- 23:25Reactive systems mindset
- 25:09Giveaway and resources
related talks
42mTackle React component complexity using Reactive Statecharts
37mReactive State Machines and Statecharts
01h 01mThe visual future of reactive applications with statecharts
36mAutotracking: Reactivity and State in Modern Ember
29mIdiomatic Ember, Sweet Spot of Performance and Productivity
59mEmber.js, and why the framework helps you unlocking unprecedented productivity.
22mMake legacy code delightful with statecharts
13mAbstract component modeling in React