2017 DevFestMN Eric Brandes
summary
Claim: the JavaScript ecosystem ships huge complexity for trivial UI — an Angular quickstart pulls 108 megabytes of node_modules, with 13,740 files, makes 38 requests and 2.2 megabytes transferred just to render an H1. Critiques specific tools (Bower, SystemJS, CoffeeScript, RxJS, generators), praises pragmatic choices (server-side rendering, PJAX, Jekyll, promises/async await, webpack or npm scripts, React+Redux and create-react-app), and warns against experimental Babel stage presets and extra package managers.
AI-written summary · about
chapters (12)
- 0:00Welcome to Victorian JavaScript
- 7:06JavaScript history and evolution
- 11:16JavaScript fatigue and frameworks
- 12:00Server-side vs client-side rendering
- 16:30Package manager pitfalls
- 19:22Transpilers and code impact
- 24:55Build tools and alternatives
- 29:10Async JavaScript handling
- 33:03Critique of JS frameworks
- 39:44React and Redux recommended
- 42:51Simplifying web development
- 43:56Q&A
related talks
48mThe Victorian Age of JavaScript
40mThe state of frontend frameworks in 2023
44mJavaScript in 2017: You might (not) need a framework
49mFront Ends for Back End Developers
01h 02mThe Wrong Kind of Fast: Embracing Evidence-Based Architecture
30mTowards a simpler JavaScript ecosystem
45mDid We(b Development) Lose the Right Direction?
29mDesigning very large JavaScript applications