Speaker: Eryk Bryn
How Ember JS’s ‘run loop’ works.
Was sold on Yehuda’s talk about templates.
The Great Divide
But EmberJS leverages HTML, which is becoming more powerful.
Is a micro-library that now is the Ember Run Loop.
What Does the Runloop Do?
It’s a queue.
Erik: all about coalescing. Keeps the DOM from being updated unnecessarily.
Ember hides BackBurner from you.
Run loop is a set of queues:
Libraries can add their own queues
Is for synchronizing bindings.
2 kinds of bindings (didn’t get the details).
All the deferred actions get put here.
Render and AfterRender
Here’s where the DOM is manipulated.
The afterRender queue is where you schedule activities after Ember has manipulated the DOM.
Where objects are destroyed.
Why does Backburner exist?
- Cleaner code
- Better debugging
- Sharing the wealth
Erik asserts that the source code for Backburner is very readable.
Debugging deferred / asynchronous actions is hard.
But Backburner makes this much easier.
New York Ember meeting talks about Ember testing.