React and angular.js don't really solve the same problems (though angular 2 is incorporating some react-like techniques). React is only the V (arguably a bit of C) from MVC, where as angular.js provides all three but does a rather crappy job on V IMHO. ng-react supposedly let's you use them together but I haven't tried it yet (I plan on it).

> React is only the V (arguably a bit of C)

Yes, but beef I have with the cool kids I've worked with are they throw out the entire app: MVC, Server, etc. so they can use this magical V - then completely rewrite and wing the rest of the app "Oh it's, um, 'Flux Architecture'"

Yep. You certainly won't hear me advocate that, but I believe that people are doing it.

I'd like to read that too actually. The new place I'm working is all Angular on the front end. Seems decent enough, but I haven't tried many JS frameworks, and haven't messed with React at all, despite all the buzz about it lately.

I honestly don't know if there's any point to trying to learn it over getting better at Angular when we have so much invested in Angular, and there's a new coolest JS framework every other week anyways.