Yeah, I’m not entirely sure what the point of the original article is. We know the parts that aren’t functional (hooks, I/O). Hell, the Component itself can be wrapped in a memoizer and become unfunctional all at once, left as a side effect of reconciliation.

The point of the FP concepts introduced to React is to lessen the cognitive load of the render cycle _of an individual component_. But I think the team is pretty clear about when side effects are part of patterning (literally one of the hooks is called “useEffect”).