Is using forceUpdate slower than setState() in ReactJS?
<p>I'm experimenting with building a ReactJS app that doesn't use ReactJS components state or props for display data. Instead I use props for passing models to the component so that it will bind <code>self</code> to it, and get re-rendered on model data change.</p>

<p>I would like to keep the component state ’clean’ in such way that the component's state would only contain data about user experience related stuff. If you are familiar with Firebase, the apps works very much like when building a react app using Firebase, but it should be more declarative.</p>

<p>Because I do not use <code>component.setState({...})</code> I would like to use <code>component.forceUpdate</code>. I have read many times that you shouldn't use this method because it skips the lifecycle methods, but this is an experiment.</p>

<p>What I'm mostly interested in right now is whether it is slower than <code>setState</code> and does ReactJS do the same smart DOM diffing when an update is forced?</p>