<story><title>React v0.14</title><url>http://facebook.github.io/react/blog/2015/10/07/react-v0.14.html</url></story><parent_chain></parent_chain><comment><author>clessg</author><text>A lot of great ideas in this release and it makes me excited for the future of React.&lt;p&gt;I&amp;#x27;ve been on 0.14-rc1 and my favorite feature so far is stateless function components. So much cleaner than class-based components.&lt;p&gt;One downside is that hot reloading doesn&amp;#x27;t work with it yet (AFAIK). Hopefully that will come soon now that 0.14 is officially released. (And I believe Dan is&amp;#x2F;was on vacation.)&lt;p&gt;Andrew Clark (core contributor to Redux and creator of Flummox) just released Recompose which provides powerful capabilities for stateless components: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;acdlite&amp;#x2F;recompose&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;acdlite&amp;#x2F;recompose&lt;/a&gt;.&lt;p&gt;Some of the benefits of stateless function components as outlined in Recompose&amp;#x27;s readme:&lt;p&gt;* They prevent abuse of the setState() API, favoring props instead.&lt;p&gt;* They&amp;#x27;re simpler, and therefore less error-prone.&lt;p&gt;* They encourage the smart vs. dumb component pattern.&lt;p&gt;* They encourage code that is more reusable and modular.&lt;p&gt;* They discourage giant, complicated components that do too many things.&lt;p&gt;* In the future, they will allow React to make performance optimizations by avoiding unnecessary checks and memory allocations.</text></comment>
<story><title>React v0.14</title><url>http://facebook.github.io/react/blog/2015/10/07/react-v0.14.html</url></story><parent_chain></parent_chain><comment><author>Touche</author><text>&amp;gt; Like always, we have a few breaking changes in this release. We know changes can be painful (the Facebook codebase has over 15,000 React components), so we always try to make changes gradually in order to minimize the pain.&lt;p&gt;Since React is a semver project, from the website:&lt;p&gt;&amp;gt; How do I know when to release 1.0.0?&lt;p&gt;&amp;gt; If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you&amp;#x27;re worrying a lot about backwards compatibility, you should probably already be 1.0.0.</text></comment>