<story><title>React Tips and Best Practices</title><url>http://aeflash.com/2015-02/react-tips-and-best-practices.html</url><text></text></story><parent_chain></parent_chain><comment><author>themgt</author><text>One of the things I didn&amp;#x27;t realize at first was the degree to which Relay&amp;#x2F;GraphQL appear to effectively replace a lot of Flux: &lt;a href=&quot;http://facebook.github.io/react/blog/2015/02/20/introducing-relay-and-graphql.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;facebook.github.io&amp;#x2F;react&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;02&amp;#x2F;20&amp;#x2F;introducing-...&lt;/a&gt;&lt;p&gt;Learning Flux sort of seems like learning how to drive stick shift on an &amp;#x27;97 Civic while we wait for the new Tesla to arrive - useful, also a bit annoying. A central store architecture does seem a better match to what Relay will look like though.</text></comment>
<story><title>React Tips and Best Practices</title><url>http://aeflash.com/2015-02/react-tips-and-best-practices.html</url><text></text></story><parent_chain></parent_chain><comment><author>amelius</author><text>Let&amp;#x27;s be real. It&amp;#x27;s 2015 and we need quite some hoops to get, in most cases, some very simple data rendered on the screen. And even with all those hoops, we are still not sure that it works in all cases. Isn&amp;#x27;t it time for better tools than react? Like functional languages that support incremental computation?</text></comment>