You are right in correcting me that MVC et al. can also reference something other than frameworks like Rails. I may have jumped the gun there. > I'm not sure w

You are right in correcting me that MVC et al. can also reference something other than frameworks like Rails. I may have jumped the gun there. > I'm not sure what want/need distinction you are trying to make here. What I feel is happening in these discussions is that people take the issues they run into when creating SPA with component frameworks (state management, making calls to back ends and error handling to name a few) and present them as fundamental issues of creating web applications. When React first came out, you quickly ran into the issue that, for a bigger application, you needed to pass too many parameters through the whole stack to reach the outermost components just to update something like a counter badge, etc. Then came Redux and it 'solved' this. This issue of passing parameters down the component stack is only an issue within the context of using a stack of components. It isn't one of the issues that exist when building a web application using server side rendering. So what I mean with 'you don't need' state management in the front-end is that the issue of managing state is completely inherent to building a UI with components, it isn't an absolute problem of creating web applications.