IO • @eviltrout, SamSaffron, Jeff Atwood (@codinghorror) on Discourse • Erik Bryn • those guys from twitch.com, square, urbanspoon… EVAN IS A FAN! OF THESE PEOPLE
and supply the model • controllers manage momentary state in the UI • views help build out the dynamic parts of the UI • templates describe the UI’s HTML
listener for that event is triggered. • Early on in its response to the event, Ember opens a set of queues and starts accepting jobs. • As Ember works its way through your application code, it continues to schedule jobs on the queues. • Near the end of its response to the event Ember closes the queue-set and starts running jobs on the queues. Scheduled jobs can themselves still add jobs to the queues even though we have closed them to other code. • The runloop Guide has an excellent visualization of how jobs are run but in brief: • Scan the queues array, starting at the first until you find a job. Finish if all queues are empty. • Run the job (aka execute the callback function) • Go to step 1 ember tries to do similar! things at the same time.
• it has an object system that is consistent. • it does a lot of opinionated magic for you, so learn the magic words. • its leadership is intentionally future proofing it. • it has a cute hamster as a mascot.