Understanding JavaScript Libraries via React and the React Ecosystem
summary
A practical account of how a project at JamBon Software moves from JavaScript ignorance to working frontend: tiny website with React and Redux that uses Webpack + Babel transpile ES6 to ES5, Yarn for deterministic installs, fetch (with polyfill), Promises and thunks for async, Redux-Forms for input, ESLint, and Jest which cuts test time from minutes to under one. Notes tradeoffs around server rendering, create-react-app convenience, and looming React Fiber and patent concerns.
AI-written summary · about
chapters (40)
- 0:00Introduction
- 0:29Andrew Pinkham
- 0:43Software Consultant
- 0:58CertCycle
- 1:22JavaScript Talk
- 1:58How did I get here
- 2:25This talk is fundamentally incomplete
- 3:02How I got here
- 3:44The most important part
- 3:56Django people go
- 4:24I was asking this question
- 4:37History of HTML
- 4:47What is HTML
- 5:05HTML History
- 6:03JavaScript
- 7:17Core Problems
- 7:59Learning JavaScript
- 9:01Language Versions
- 9:19JavaScript Spec
- 10:06Transpilation
- 11:54Webpack
- 13:03Environment Tools
- 13:58Conclusion
- 14:30Library vs Framework
- 15:09The DOM
- 15:25The View
- 15:39Model Controller
- 16:11Dynamic Content
- 16:32Reactive Programming
- 17:08Model or State
- 17:34React vs MVC
- 18:36How React works
- 19:16Flux architecture
- 19:53React Redux
- 20:12Synchronization
- 20:58Testing
- 22:06Django Templates
- 23:12JavaScript DOM
- 24:23React App
- 25:16React Fibre
related talks
44mJavaScript in 2017: You might (not) need a framework
36mModern Javascript with React and Redux
30mTowards a simpler JavaScript ecosystem
49mNavigating the React Solar System
20mMoving JS from Libraries to Polyfills
50mNavigating the React Ecosystem
10mExploring React My Own Way
27mI Heard React Was Good