<story><title>Facebook Announces React Fiber, a Rewrite of Its React Framework</title><url>https://techcrunch.com/2017/04/18/facebook-announces-react-fiber-a-rewrite-of-its-react-framework/</url></story><parent_chain><item><author>nightski</author><text>The benefits you acknowledge (distribution) are not because of the tech but in spite of it.&lt;p&gt;At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative.  That alternative could be distributed to a large percentage of desktops in a relatively quick manner saving billions if not trillions of dollars in wasted productivity.&lt;p&gt;It will never happen though.&lt;p&gt;* EDIT: This comes from someone who uses React, Redux, webpack, etc.. daily</text></item><item><author>acemarke</author><text>Your comment seems to be a bit of a non-sequitur.&lt;p&gt;Application development is complex, period.  Posix development is complicated.  Qt is big and complicated.  Makefiles are complicated.  Autotools is complicated.  Big Java server apps are complicated.  C++ is complicated.  We&amp;#x27;ve just hit the point where people are trying to do the same thing in a browser.&lt;p&gt;Would you prefer to build your application using Make, Scons, Waf, CMake, QMake, Tup, Bash scripts, Maven, Gradle, Ant, Buck, or something else?  The build tool question is _totally_ solved, right? :)&lt;p&gt;Yes, the JS community has been reinventing a number of wheels.  Yes, the browser environment and JS standard lib have weaknesses.  On the other hand, it&amp;#x27;s also allowed developers to build useful applications that are immediately distributable to pretty much anyone who has an internet connection.</text></item><item><author>metalliqaz</author><text>I admire your exceptional work cataloguing these resources.  However, just one look at that giant horde of links is, to me, a perfect demonstration of why the front-end development ecosystem is way out of control.&lt;p&gt;Its amazing to me that the autoconf&amp;#x2F;automake&amp;#x2F;libtool system for making write-once-run-everywhere *nix applications is downright simple by today&amp;#x27;s standards.&lt;p&gt;Every year the hot libraries change, the build tools change, the metalanguages, the data formats, even the damn paradigms change.  Each generation requires more layers trying to fix up the underlying evil that nobody who soaks themselves in the matter will admit: the browser is a bad app platform and javascript is a bad language.  Both have been pressed into serving a purpose for which neither were designed.</text></item><item><author>acemarke</author><text>I&amp;#x27;ll repeat the comment I made in the &amp;quot;React 15.5&amp;quot; thread a couple weeks ago (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=14063818&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=14063818&lt;/a&gt;):&lt;p&gt;For those who are interested in some of the details of the work that&amp;#x27;s going on, Lin Clark&amp;#x27;s recent talk on &amp;quot;A Cartoon Intro to Fiber&amp;quot; at ReactConf 2017 is excellent [0]. There&amp;#x27;s a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 migration is at [2], and the follow-up issue discussing the plan for the &amp;quot;addons&amp;quot; packages is at [3].&lt;p&gt;I&amp;#x27;ll also toss out my usual reminder that I keep a big list of links to high-quality tutorials and articles on React, Redux, and related topics, at &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&lt;/a&gt; . Specifically intended to be a great starting point for anyone trying to learn the ecosystem, as well as a solid source of good info on more advanced topics. Finally, the Reactiflux chat channels on Discord are a great place to hang out, ask questions, and learn. The invite link is at &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reactiflux.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reactiflux.com&lt;/a&gt; .&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=ZCuYPiUIONs&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=ZCuYPiUIONs&lt;/a&gt;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;react-implementation.md#react-fiber&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&amp;#x2F;blob&amp;#x2F;master...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;8854&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;8854&lt;/a&gt;&lt;p&gt;[3] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;9207&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;9207&lt;/a&gt;</text></item></parent_chain><comment><author>julian_1</author><text>No-one could even agree on making HTML5 valid XML - in order to leverage all the tools and knowledge that exist in that space.&lt;p&gt;Not that I even like XML. But having another XML dialect that&amp;#x27;s not actual XML shows that the only hope is to build valid tools and abstractions on top of all the crud.</text></comment>
<story><title>Facebook Announces React Fiber, a Rewrite of Its React Framework</title><url>https://techcrunch.com/2017/04/18/facebook-announces-react-fiber-a-rewrite-of-its-react-framework/</url></story><parent_chain><item><author>nightski</author><text>The benefits you acknowledge (distribution) are not because of the tech but in spite of it.&lt;p&gt;At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative.  That alternative could be distributed to a large percentage of desktops in a relatively quick manner saving billions if not trillions of dollars in wasted productivity.&lt;p&gt;It will never happen though.&lt;p&gt;* EDIT: This comes from someone who uses React, Redux, webpack, etc.. daily</text></item><item><author>acemarke</author><text>Your comment seems to be a bit of a non-sequitur.&lt;p&gt;Application development is complex, period.  Posix development is complicated.  Qt is big and complicated.  Makefiles are complicated.  Autotools is complicated.  Big Java server apps are complicated.  C++ is complicated.  We&amp;#x27;ve just hit the point where people are trying to do the same thing in a browser.&lt;p&gt;Would you prefer to build your application using Make, Scons, Waf, CMake, QMake, Tup, Bash scripts, Maven, Gradle, Ant, Buck, or something else?  The build tool question is _totally_ solved, right? :)&lt;p&gt;Yes, the JS community has been reinventing a number of wheels.  Yes, the browser environment and JS standard lib have weaknesses.  On the other hand, it&amp;#x27;s also allowed developers to build useful applications that are immediately distributable to pretty much anyone who has an internet connection.</text></item><item><author>metalliqaz</author><text>I admire your exceptional work cataloguing these resources.  However, just one look at that giant horde of links is, to me, a perfect demonstration of why the front-end development ecosystem is way out of control.&lt;p&gt;Its amazing to me that the autoconf&amp;#x2F;automake&amp;#x2F;libtool system for making write-once-run-everywhere *nix applications is downright simple by today&amp;#x27;s standards.&lt;p&gt;Every year the hot libraries change, the build tools change, the metalanguages, the data formats, even the damn paradigms change.  Each generation requires more layers trying to fix up the underlying evil that nobody who soaks themselves in the matter will admit: the browser is a bad app platform and javascript is a bad language.  Both have been pressed into serving a purpose for which neither were designed.</text></item><item><author>acemarke</author><text>I&amp;#x27;ll repeat the comment I made in the &amp;quot;React 15.5&amp;quot; thread a couple weeks ago (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=14063818&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=14063818&lt;/a&gt;):&lt;p&gt;For those who are interested in some of the details of the work that&amp;#x27;s going on, Lin Clark&amp;#x27;s recent talk on &amp;quot;A Cartoon Intro to Fiber&amp;quot; at ReactConf 2017 is excellent [0]. There&amp;#x27;s a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 migration is at [2], and the follow-up issue discussing the plan for the &amp;quot;addons&amp;quot; packages is at [3].&lt;p&gt;I&amp;#x27;ll also toss out my usual reminder that I keep a big list of links to high-quality tutorials and articles on React, Redux, and related topics, at &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&lt;/a&gt; . Specifically intended to be a great starting point for anyone trying to learn the ecosystem, as well as a solid source of good info on more advanced topics. Finally, the Reactiflux chat channels on Discord are a great place to hang out, ask questions, and learn. The invite link is at &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reactiflux.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reactiflux.com&lt;/a&gt; .&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=ZCuYPiUIONs&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=ZCuYPiUIONs&lt;/a&gt;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;react-implementation.md#react-fiber&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markerikson&amp;#x2F;react-redux-links&amp;#x2F;blob&amp;#x2F;master...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;8854&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;8854&lt;/a&gt;&lt;p&gt;[3] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;9207&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;facebook&amp;#x2F;react&amp;#x2F;issues&amp;#x2F;9207&lt;/a&gt;</text></item></parent_chain><comment><author>ZenoArrow</author><text>&amp;gt;&amp;quot;At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative.&amp;quot;&lt;p&gt;You mean like Dart?&lt;p&gt;Besides, languages that target WebAssembly are almost certainly going to evolve to fit that space.</text></comment>