An Illustrated Guide to Ember
summary
Ember application for school finance displays thousands of rows in a semantic table; Ember 1.6 uses metamorph script tags causing rendering to take 6 seconds to 1–2 seconds for small page sizes. Upgrading to Ember 1.8 with HTMLBars rendering engine replaces string fragments with DOM nodes and renders about four times as many rows, cutting latency. Stack uses Rails API, Ember Data and CoffeeScript, then moves from pagination hacks to a stateful redesign with infinite scroll; deployed to districts and handling real load.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:36Metamorph Script Tags
- 11:41Amber 1 8
- 12:06Html Bars Rendering Engine
- 18:48The Release Schedule
- 21:28Amber and User Testing
- 22:11Mixpanel
related talks
22mUsing Ember to Make the Seemingly Impossible Easy
22mUsing Ember to Make the Seemingly Impossible Easy
48mInside Glimmer: What Makes Ember's Rendering Engine Tick
31mEmber on Rails: #REALTALK
46mArt and Science of Shipping Single Page Apps with Ember.js
36mPanel: Ember at Scale
40mEmber's Technical Foundations – And How They Are Changing
01h 10mPanel: the future of Ember
