#dadt (Dojo already did that)
summary
Claims that Dojo invented a lot of patterns now taken for granted: module loading that moves from blocking sync XHR and eval to AMD asynchronous module loading (inspired by James Burke’s work), HTML-node metadata via the data-dojo-type attribute, deferred/promise primitives, a monolithic UI library (Dijit) with accessibility and i18n built in, and a build system that eventually moves from Rhino to node. Concrete tradeoffs include years spent preserving backwards compatibility and a multi-year migration to AMD.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 13:05Origin Policy
- 13:25Requiredjs
- 17:19UMD
- 18:53JavaScript
- 21:32UI Libraries
- 26:42Events
- 28:07Binding
related talks
46mdojo.Patterns for Lovers of JavaScript
25mModern JavaScript
01h 32mIOC + Javascript
38m"Design Patters for Modern JavaScript"
04mDevelopment of JavaScript applications
41mThe future is modules not frameworks. JS modules Architecture demo.
39mDOM it, forgive, forget, embrace
21mAsk not what JavaScript can do for you