Why is React just the V in MVC?

Why do many people think that React is just the V in MVC?
my understanding is as follows: the jsx, in
1.react includes the rendering logic, which can be regarded as V, and together with the render/diff, behind it, the rendering of the component
the state and prop, of the 2.react component itself can also be regarded as M, responsible for the data state of the component, M is not limited to state
3 shared by the component tree. The event / behavior encapsulated by the component itself can also be thought of as C, which is responsible for setting and changing data. C is not limited to redux action
. Therefore, without access to redux, a single functional component itself can also be regarded as a local MVC model

Mvc react.js

Mar.29,2022

if you are talking about an offline application, that is, an application that does not require a back-end response, it can be divided like this.

but generally speaking, when we talk about MVC , we regard the system as a whole. In this case, the state , prop , and event / behavior all serve the rendering view , so React is only a V in a system.

React is considered to be the framework of the view layer because it is based on components, everything is components, and components are the basis of rendered pages, regardless of the jsx,methods,state,props contained in components, are internal to the component. You are wrong to say that state and prop in React can be regarded as M, because React itself does not have the concept of state management, which is why there is something like Redux, because React itself cannot handle the data interaction of various components, after all, it is only the V layer.

MVVM ViewModel is not a simple V

Previous: Flex-direction: column has no effect?

Next: Android studio installs virtual devices and downloads slowly, but copying the address to the browser downloads quickly. Can you download it and put it in the appropriate directory?