Post

tried writing this blog 3 times but it’s really boring, so here’s the short version: React won. Every mainstream f/w now implements its ideas, and developed their own ecosystems. The ones that didn’t, lost and died. This implies there’s no _strong_ reason to not pick one of the other winners.

but what about signals

React should have adopted signals before going nuts on a compiler or RSCs IMO. My 5 year prediction is a solid one… 😜

I still genuinely don't know what "React adopt signals" would _mean_ at a technical level. Per other comments in this thread, React works at the component level. What would a hypothetical native-to-React signals integration do differently?

It would have to have been something new. Breaking likely. Signals would allow: - finer grained updates than “component” e.g. jsx fragments - state/data flow that isn’t tied to component hierarchy and doesn’t need to rerender (or subscribe to a store to rerender) itself and its children

And honestly just the savings from useComputed being lazy unlike useMemo in all these apps would have been staggering.

The cynical reason why this never happened in React would be because it devalues React. If you don't need components to build complex trees of state, you barely need components at all. And then you barely need react at all. Working on React or a React FW subconsciously biases away from that.

I think it has to go even deeper. Props tracking needs to be fine grained as well. React would become more like Solid. And it would mean loads of breaking changes.

You still need components for the domain modeling benefits. So signals let you re-render at the element level? That’s pretty neat. Guess you could do that by composing even smaller components but that probably gets unwieldy 🤔