DownTheRabbitHole.js – How to Stay Sane in an Insane Ecosystem
summary
Built an HTML5 educational game called space forensics for NASA and the project proves the talk favors concrete choices: using ES6 with Babel, webpack/brunch, hot loaders and automation; front end stack centered on lodash, React and Redux; D3 and RxJS for data and streams; NPM’s explosion of modules creates both power and risk — the left-pad incident breaks many chains. Decision criteria are size, audience, team skill, lifetime and whether the tool actually reduces risk.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:52Space Forensics
- 3:49Power Struggle
- 5:34In the meantime.
- 6:40node.js & npm
- 10:21Wait... "modules"?
- 11:10JavaScript Tooling
- 12:27On the horizon
- 14:41One size does not fit all
- 17:18Not just a technical problem!
- 17:40Transpiled Languages
- 21:49Invest in great tooling
- 26:39Philosophy
- 30:03Small vs. Big
- 31:08Documentation
- 33:10Functional Programming
- 35:50Options from the "Big Boys"
- 37:18Other great libraries
- 39:02You cannot stop swimming
related talks
45mDownTheRabbitHole.js – How to Stay Sane in an Insane Ecosystem
27mUnderstanding JavaScript Libraries via React and the React Ecosystem
49mI'm good at JavaScript, I swear.
57mJavaScript Framework Cage Match
58mAlways crashing in the same car (the state of front end web development in 2022)
29mJavaScript and Game Development
32mWhat's Happening in the JavaScript Ecosystem?
42mJavaScript in All the Creative Places