Client Side MVC and The Gosh Darn Back Button

on YouTube ↗40m

" summary

Shows how long-lived single-page apps at Shopify admin leak memory (examples: jQuery.data cache causing retained DOM, event-handler closures, and identity-map growth) and how frameworks mitigate it: Backbone's view.remove, Ember/Batman's lifecycle hooks and bindings, and changing from a global cache to storing data on nodes. Demonstrates Batman.js powering the admin, measures a problematic chat client ballooning 50MB to 1GB, and argues lifecycle-managed enter/exit callbacks as the practical fix.

AI-written summary · about

" chapters (10)

1. 0:00The problem of memory leaks
2. 1:20Old world vs new world
3. 3:15jQuery data and memory leaks
4. 7:13JavaScript garbage collection
5. 11:51Why leaks matter today
6. 13:40Lessons from iOS development
7. 17:38Frameworks and lifecycle
8. 22:57Data binding as a solution
9. 27:24Trade-offs and protection
10. 30:04Q&A and final thoughts

" related talks

• 29mTo a Single Page Web App and Back AgainNicholas Simmons · Red Dot Ruby Conference 2014
• 01h 29mClient-Side UI SmackdownCraig Walls · SpringOne2GX 2012
• 33mPitfalls and Opportunities of Single Page ApplicationsJörn Zaefferer · jQuery Conference 2012 San Francisco
• 46mArt and Science of Shipping Single Page Apps with Ember.jsJesse Cravens · FITC Toronto 2015
• 54mTaking JavaScript Seriously with Backbone.jsJeremy Ashkenas · Web Directions Code 2013
• 51mBuilding Amazing Single Page Applications the Right WayJustin Meyer · GOTO Chicago 2015
• 49mBuilding Web Applications with Ember.jsYehuda Katz · HTML5DevConf 2013
• 30mBeyond the DOM: Sane Structure for JS AppsRebecca Murphey · jQuery Conference 2012 San Francisco