Why React is not Reactive
summary
Compares functional-reactive libraries such as RxJS with React’s model by building a “Reactive React” that highlights differences between push-based (observable/stream) and pull-based (React’s render-driven) data flow. Explains concrete pitfalls of imperative event handlers like async setState and race conditions, and shows how React’s choice to treat Scheduling as a core design principle enables features such as async rendering and Suspense.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:43HOW IT FEELS TO LEARN REACTIVE
- 9:27WHY DOESN'T REACT USE STREAMS?
- 10:19COUNTER
- 10:35REACTIVE-REACT: COMPONENT A
- 13:04BLINK
- 13:55FLAPPY BIRD
- 16:05TOO MANY UPDATES
- 19:59MAYBE WE SHOULDN'T PUSH EVERYTHING
related talks
31m(React)ive State Management: Enter RxJS
36mModern React and the case for Reactive State Management
27mFunctional Reactive Programming: What Does It Solve? Does It Solve Things? Let's Fi...
39mIntroduction to Reactive Programming with React
36mRxJS: A Better Way to Write Frontend Applications
20mReact Realism: Is there another alternative?
28mReactive Programming Demystified Drink the Kool-Aid
27mBe More Functional and Reactive in React