Angular is a monolithic framework, with all of the pros/cons that that brings.

Reactjs is simply the view layer, and plays nicely with other libraries.

Think of react.js as a Directive alternative - it's not as full-featured as Angular but you could replace Angular Directives with it.

TL;DR: Ember and Angular are more full-featured than React.js. And Angular gives you the most bang per byte downloaded.

angularjs is mvc (Model View Controller)

react is only the V(iew), so you can blend AngularJS with ReactJS.

The most popular post (about Angular vs React) is on http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-Angu... , but it's kinda subjective i suppose as he works on the React team.

(Note: I use AngularJS, but haven't used ReactJS. So if i'm wrong, please correct me).

Here is a nice comparison though http://www.reddit.com/r/javascript/comments/1v4glc/react_vs_...

The Reddit link seems much less objective than Pete Hunt's overview (e.g. the last point about React not providing code modularity is flat out wrong)

I wrote a frontend framework comparison essay here ( http://lhorie.github.io/mithril/comparison.html ). It's focused heavily on Mithril.js, but might be useful for someone evaluating frameworks.

FWIW, I've used Angular extensively for the past few years and some of the reasons I wrote Mithril (which has a virtual-dom based engine like React) were because 1) Angular performance issues are really hard to fix, 2) I feel some of the design decisions in Angular are fundamentally flawed.

Thank you for writing Mithril; it's a breath of fresh air coming from the complexity of Angular. Not to mention the small size (5kb!) - that'll be especially useful when we build our JavaScript embed widget.

(React dev here)

I myself have been guilty of spreading this "React is just the view" mentality as an easy argument to convince people to try it. However, in reality, you can't really compare framework X's view with React view just because they're both called "view". React's whole architecture and paradigm makes it so that you don't need controllers or, very often, not even models.

In this regard, "bang per byte downloaded" is very misleading (it already kinda is?).

That is correct, but I will say that React can enable a different application structure in a way that other view layers (i.e. more "normal" template engines) do not. React can be treated as a function (pass in input, out comes a UI based solely on that input) and I've found that this lets me simplify other aspects of my code.

Thanks for your comments both of you I am trying to figure out which I should learn being an ASP.Net developer

PS - FYI http://www.google.com/trends/explore#q=react.js%2C%20ember.j...