Yes, I agree with you that the problem is exactly that React's decision to create a "library" that ostensibly only addresses the View layer creates a situation where it's very difficult to create something that's "only a View," whether you're working in Classes, with hooks, or what have you. That's why for any significant sized application, you need to add at least one "library" that addresses the business layer. I would argue that the ideal is pure functional components (or, at worst, components that use a small amount of useState/useReducer) that are directly wired into Redux with mapStateToProps/mapDispatchToProps creating the wiring in a thin layer around the component. I've been thinking about expanding the series to 4 parts for "what to do instead," but AtlasUP just started our own publication and I have other stuff I want to write for that so who knows if it will happen.