there's a big problem with React's useContext

Wait I dont understand why would you suggest putting the context provider in the highest possible node in the tree? Just after saying that components re-render their children unnecessary after context value change?

if you pass it at a low part of a subtree that renders a lot, and the value changes a bunch, and many parts of the app depend on that data, it can cause issues

Grab your popcorn 🍿 Our React Native for TV guide is here, packed with the latest techniques and best practices. Don't miss out on this essential update to keep your apps running at peak performance 🚀 Download it now 🔗

`use-context-selector` is an amazing abstraction layer that solves this problem

Yeah. This is what I dislike most with React's useContext. Better alternatives: - MobX - Zustand - Jotai

Did you manually speed up the video? My setting says 1x but it sounds like 1.5-2x

I was hoping to see a mention of useMemo and React.memo

React should just provide better global state handling out of the box. Its such a common use case.

Hm, useContext is great for avoiding prop drilling in components, but this video seems centered around application-level state - for that, use something like Redux / Zustand Application state gets messy with Context, and having 12 different contexts on the top-level is not ideal

React === Problems

love these videos. learning a lot about react through these short bites. just a note, i had to slow down the speed to .75 to really grasp what you're saying.