One of the first questions people ask when considering React for a project is whether their application will be as fast and responsive as an equivalent non-React version. The

It's a common pattern in React to wrap a component in an abstraction. The outer component exposes a simple property to do something that might have more complex implementation

Trying to compare and contrast React with WebComponents inevitably results in specious conclusions, because the two libraries are built to solve different problems. WebComponents

Currently, in a component's render, you can only return one node; if you have, say, a list of divs to return, you must wrap your components within

setState void setState( function|object nextState, [function callback] )

Updating: componentWillReceiveProps void componentWillReceiveProps( object nextProps

getDefaultProps object getDefaultProps() Invoked

statics object statics The statics

Mounting: componentWillMount void componentWillMount() Invoked

replaceProps void replaceProps( object nextProps, [function callback] )