JavaScript in 2017: You might (not) need a framework

on YouTube ↗44m

" summary

Argues that React-style component structure can start as plain JavaScript and be evolved stepwise into a production build using npm, Mustache, RequireJS, then native ES2017 imports + async/await transpiled by Babel into AMD, bundled and minified with webpack bundle -> single bundle.js, and finally swapped to JSX/React with react-devtools. Demonstrates a small site with nav, list item and terminal components that works at each stage, notes the surprising cost: dozens of tooling packages, an obligatory build step, and added complexity around dependency ordering and caching.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 2:25React
3. 11:47Template Loaders
4. 13:06Using a Template Engine
5. 38:48React Tools
6. 40:01The Difference between Web Pack and React

" related talks

• 27mUnderstanding JavaScript Libraries via React and the React EcosystemAndrew Pinkham · DjangoCon US 2017
• 30mTowards a simpler JavaScript ecosystemGil Tayar · JSHeroes 2023
• 45mNo framework frontends in practice - use the platform!Karol Horosin · 4Developers Katowice 2019
• 41mYou Really Don't Need All That JavaScript I PromiseStuart Langridge · Pixel Pioneers Bristol 2022
• 34mTowards a simpler JavaScript ecosystemGil Tayar · ReactNext 2024
• 54mModern JavaScript For Web DinosaursRyan Preece · NDC Sydney 2019
• 59mNo Strings Attached: JavaScript without Webpack, Transpilers, or FrameworksAshley M Grant · NDC Minnesota 2019
• 54mJavaScript Essentials for Programming with ReactVenkat Subramaniam · Developer Summit 2020