Why React?
summary
Eventbrite moves its frontend from Backbone/Marionette to React and justifies it with concrete wins: JSX declarative templates that compile to createElement, component-driven UIs with prop/state APIs, predictable state-driven updates via setState, and efficient updates via virtual DOM diffing / reconciler (Fiber). Tooling includes server rendering with react-dom/server hydrate, tests with Enzyme + Jest, and reuse in a shared Eventbrite design system plus React Native. Team scales — 25 engineers attend training — so migration proves practical and productive.
AI-written summary · about
chapters (14)
- 0:00Introduction and setup
- 3:50Speaker introduction
- 6:18JSX and declarative UI
- 11:21Component-driven architecture
- 14:33Logic-centric approach
- 21:23State-driven interactivity
- 29:37Virtual DOM and reconciliation
- 33:12Beyond core React features
- 33:34Server-side rendering
- 37:11Testing React components
- 42:13React Native introduction
- 45:25React's unopinionated nature
- 49:06Additional React considerations
- 51:15Closing remarks and thanks
