Recs.
Updated
SpecsUpdate
Pros
Pro Good debugging tools
React has an official Chrome Extension which is used as a developing and debugging tool. It can be used to quickly and painlessly debug your application or view the whole application structure as it's rendered.
Pro Synthetic Events
DOM differences and spec inconsistencies are abstracted away. Bubbling works correctly. onChange fires onChange since that's what you'd expect (vs reality where some browsers that don't fire the change handler onBlur for some inputs). You also get top level events for free. You can declare your intention and React will figure out the optimal way to attach event handlers.
Pro Flux architecture pattern
Flux is a platform agnostic pattern which can technically be used with any application or programming language.
One of Flux' main features is that it enforces uni-directional data flow which means that views do not change the data directly.
With React this is useful because this way it's easier to understand an application as it starts getting more complicated. By having two-way data binding, lead to unpredictable changes, where changing one model's data would end up updating another model. By using the Flux architecture, this can be avoided.
Cons
Con Limitation as it is the Facebook way
React is not the best solution for every case.
React is more like "if server solves the problem then the container displays the output" type than other libs. If you are using electron you will feel it would just be better without react for handling DOM.
Con Large file size
React's react.min.js
is 145.5KB in size. It's much larger than some other libraries that offer roughly the same features and it's almost the same size as some MV* frameworks such as Angular or Ember that offer more features out of the box.
Although, it should be mentioned that sometimes having a smaller library may force developers to reinvent the wheel and write inefficient implementations on features that React already has. Ending up with a larger application that's harder to maintain and/or that has bad performance.
Con Forcing developer to use react way (state/refs) for DOM but they are not really mature
You can use document.getElementById to obtain DOM element that is placed in other script. However, you are not allowed to use document.getElementById for the element that is placed in same script(JSX).
Con Not a complete solution
React does not do everything for the developer, it's merely a tool for building the UI of a web app. It does not have support for routing or models, at least not out of the box. While some missing features can be added through libraries, to start using React and use it in production, you still would need to have experience, or at least a good grasp on what the best libraries to use would be.
Con You have to learn a new syntax
Requires to learn a custom syntax, JSX that has some gotchas and introduce complexity, a steeper learning curve, and incompatibility with other tools.
Though you can opt out from JSX and use vanilla JS instead. But that is not recommended since it adds a lot of unneeded complexity which JSX tries to avoid.
Recommendations
Comments
Flagged Pros + Cons
Pro Pluggable
Can be easily utilized with other libraries and frameworks like Angular, Backbone, etc.