A brief history and mishistory of modularity

on YouTube ↗30m

" summary

Argues that modularity’s value is practical not ideological: npm shows thousands of packages with ~224 million downloads a day, the left-pad incident exposes fragile transitive deps, and browserify can spend ~400ms walking the module tree, making many tiny modules hurt runtime. Recommends decomposing around likely-to-change decisions, isolating hard parts, preferring disposable bits over premature reuse, and measuring actual costs (downloads, dependency depth, build and runtime time) rather than prescribing smallness as a virtue.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 3:38how do you decide what goes in a module?
3. 8:25npm is the LARGEST MODULE REPOSITORY IN THE WORLD.
4. 16:36what is information?
5. 25:06how to computer?

" related talks

• 39mA brief history and mishistory of modularityAshley Williams · ffconf 2016
• 29mA Brief History of ModularityAshley Williams · JSConf EU 2017
• 19mModularity MattersAnna Gerber · Web Directions South 2013
• 01mMark Richards at DDD EuropeMark Richards · DDD Europe 2025
• 41mThe future is modules not frameworks. JS modules Architecture demo.Brian Cavalier, John Hann · JSConf US 2011
• 36mUnbundling the JavaScript module bundlerLuciano Mammino · Codemotion Rome 2018
• 48mMicroservices? Monoliths? Modules!Eberhard Wolff · Software Architecture fwdays'22
• 35mKnowing Your TCO (Total Cost of Ownership)Owen Buckley · Reliable Web Summit 2021