Yeah, I think it's something you just have to get a feel for over time. Sometimes prop drilling is the lesser of two evils, other times it makes more sense to break related state up into a shared context.
At least the React ecosystem as a whole seems to have broken free from the delusion that Redux is the be-all-end-all of state management. Those were dark days.
> It's really quite simple and elegant. Svelte's model would likely be more complex tbh.
Prop drilling in Svelte is exactly the same complexity.
useState() wouldn’t exist because Svelte doesn’t need a virtual DOM and the compiler takes care of reactivity (per the famous React vs Svelte meme).
Stores are way, way simpler than redux reflux whatever else.
I prefer an explicit function call over compiler voodoo magic, especially when it comes to reactivity (of which can have performance implications). Any solution where a compiler is changing the semantics of my code on the fly is just a hard pass.
It's really quite simple and elegant. Svelte's model would likely be more complex tbh.