The future is modules not frameworks. JS modules Architecture demo.
summary
Argues that real benefit comes from concrete modules not vague frameworks and proves it by building a small client app — a “pirity” picker — that runs under an AMD loader and swaps implementations at load time. Uses AMD module format, maps querySelectorAll to Sizzle, loads promises/deferred, CSS and text plugins, and boots components with curl.js and an IoC spec via wire. Notes a measurable performance gotcha: inline anonymous handlers compile worse than hoisted functions, and shows dozens of reusable modules already in production.
AI-written summary · about
chapters (33)
- 0:00Intro
- 1:59Modules
- 2:49Frameworks
- 3:44Web Libraries
- 4:01Micro Libraries
- 4:26Code Infiltration
- 5:19Coding dysentery
- 6:04Example of dysentery
- 7:27What is the coding utopia
- 8:34Code example
- 10:07Is this feasible
- 10:31We need to take modules
- 11:21EventListener
- 12:23W3C
- 12:41Can we have modules today
- 13:08ECMO standards
- 13:51HTML5 CSS3
- 14:02REST API
- 14:18Common JS Proposed Standards
- 15:48AMD
- 16:42Standards dont cover everything
- 17:00How do you deal with that
- 17:17Inversion of control
- 17:55AMD module format
- 21:34AMD momentum
- 22:19Plugins
- 22:43Other modules
- 24:05Dojo
- 25:09Write a module
- 27:50Demo
- 31:11Component structure
- 32:12AMD defined module
- 38:51Wire
