What Can We Learn With JavaScript Fatigue

on YouTube ↗19m

" summary

Claim: JavaScript fatigue comes from a mindset not mere volume, so focus on when a dependency actually solves a problem. Evidence includes registry scale figures like NPM: 568,191 packages and 447 new packages per day and registry growth (downloads from 480k to 480M). Concrete tooling examples: mocha chai babel react webpack and Unix‑style single‑purpose modules. Advice: prefer small incremental builds, TDD to limit decisions, and only add abstractions when their cost is justified.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 0:13Javascript Fatigue
3. 3:57Premature Optimization
4. 4:56Analysis Paralysis
5. 14:58Not Getting Ahead of Yourself
6. 17:49Strive To Be Lazy

" related talks

• 23mWhat Can We Learn With JavaScript Fatigue?Lucas Fernandes Da Costa · Frontend United 2018
• 39mWhat Can We Learn With JavaScript Fatigue?Lucas Fernandes Da Costa · THE CONF 2017
• 23mWorse is Better: The Upside of JavaScript FatigueKevin Lacker · ReactEurope 2017
• 41mThe Future of JavaScript Package ManagementDarcy Clarke · OpenJS World @ Open Source Summit Europe 2023
• 19mNavigating JavaScript UserlandZeke Sikelianos · DotJS 2016
• 06mLightning talk from Andrey SitnikAndrey Sitnik · ReactiveConf 2017
• 35mKnowing Your TCO (Total Cost of Ownership)Owen Buckley · Reliable Web Summit 2021
• 35mFighting the Front-end FatigueBenedek Gagyi · JSHeroes 2017