But ReactJS isn't a full replacement for AngularJS (and I don't see why people apparently fail to make that distinction); React is just the V in MVC, Angular is / can be the rest.
I've seen many people repeating it; but I don't know what it even means.
It definitely is the V - since it renders the view.
But it is also the C - a component encapsulates the view and view logic together. From within the component, you have lifecycle events: when the component is mounted for the first time, whenever it receives new properties, when it is unmounted etc. In any of these events, you can receive data from the external world through AJAX calls. Or you can set up AJAX calls from outside the component, and in its callback, ask React to re-render the component. There are as many ways to update the data model inside the component as we can possibly do with Javascript and callbacks. This is exactly what a Controller in a traditional MVC does: orchestrate data flow between the external world and the view. React does it beautifully.
React can also be the M, or it can compose it into the component. You can have your own validation methods and business logic that mutates the state in the component (a component is simply a Javascript object with state); or you can compose your custom Javascript object or something like Backbone.model, and keep all your logic in there.
And you can use react-router for routing. What else do we need to compare React with Angular?
I think the point is a bit moot. Since it’s just JavaScript, you can put pretty much any logic in a React component just like you could also put any kind of logic in an PHP template or inside a view in iOS.
Haven't used ReactJS much but it looks promising in solving the problems created by AngularJS for instance its push-and-pull mechanism for data binding is efficient than angular's 2-way binding using watches...
> React is just the V in MVC, Angular is / can be the rest.
that's why its more of a micro-framework, its pluggability with other frameworks makes it customisable according to the proj requirements
There are a lot of routers, http abstractions etc. out there. What people mean is "use React, along with some of the readily available modular ecosystem that exists already"
