I'm excited for relay's new core api to be released, as well.
Me too! More info is available in that blog post: https://news.ycombinator.com/item?id=14142196.
Facebook Announces React Fiber, a Rewrite of Its React Framework
31–40 of 422 posts
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#32I'll repeat the comment I made in the "React 15.5" thread a couple weeks ago ( https://news.ycombinator.com/item?id=14063818 ): For those who are interested in some of the details of the work that's going on, Lin Clark's recent talk on "A Cartoon Intro to Fiber" at ReactConf 2017 is excellent [0]. There's a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 m…
Your link [1] seems to be broken (https://github.com/markerikson/react-redux-links/blob/master...) just a heads up.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#33I'll repeat the comment I made in the "React 15.5" thread a couple weeks ago ( https://news.ycombinator.com/item?id=14063818 ): For those who are interested in some of the details of the work that's going on, Lin Clark's recent talk on "A Cartoon Intro to Fiber" at ReactConf 2017 is excellent [0]. There's a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 m…
Your link [1] seems to be broken ( https://github.com/markerikson/react-redux-links/blob/master... ) just a heads up.
Whoops, that's what I get for literally copying and pasting my comment :) Fixed - thanks!
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#34Sorry, it wasn't entirely clear to me from the article. Is React Fiber going to be a completely new project, or is it just a name for the new release? It seems like the latter to me since there's no API changes...
It's a rewrite of the internals, particularly the diffing/reconciliation algorithm. React Fiber involves effectively re-implementing the JS call stack using a data structure called "fibers" to track work that needs to be done.
The question still stands; will we be bumping a version number, or changing a package name?
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#35Earlier quoted context omitted.
It's a rewrite of the internals, particularly the diffing/reconciliation algorithm. React Fiber involves effectively re-implementing the JS call stack using a data structure called "fibers" to track work that needs to be done.
The question still stands; will we be bumping a version number, or changing a package name?
It's a major version release. v15.5 added deprecation warnings, v15.6 will add a few more warnings and fixes, and v16.0 will be a major release that includes the Fiber internals turned on. (This release path is described in the issues I linked in my earlier comment, particularly https://github.com/facebook/react/issues/8854 ).
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#36I'll repeat the comment I made in the "React 15.5" thread a couple weeks ago ( https://news.ycombinator.com/item?id=14063818 ): For those who are interested in some of the details of the work that's going on, Lin Clark's recent talk on "A Cartoon Intro to Fiber" at ReactConf 2017 is excellent [0]. There's a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 m…
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.
Its amazing to me that the autoconf/automake/libtool system for making write-once-run-everywhere *nix applications is downright simple by today's standards.
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.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#37React will die by the weight of the frameworks and libraries that have duplicated effort and created more confusion and divide amongst the developer community.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#38Does this mean something for someone starting in React Native or the changes in that regard are just under the hood?
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#39React will die by the weight of the frameworks and libraries that have duplicated effort and created more confusion and divide amongst the developer community.
It's made my life infinitely easier writing front end apps that need to keep state and update when the data changes. Remember the old days of backbone and marrionette? Remember even older, having horrible jquery sprinkled around everywhere?
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#40I'll repeat the comment I made in the "React 15.5" thread a couple weeks ago ( https://news.ycombinator.com/item?id=14063818 ): For those who are interested in some of the details of the work that's going on, Lin Clark's recent talk on "A Cartoon Intro to Fiber" at ReactConf 2017 is excellent [0]. There's a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 m…
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. Its amazing to me that the autoconf/automake/libtool system for making write-once-run-everywhere *nix applications is downright simple by today's standards. Every year the hot libraries change, the build too…
Your comment seems to be a bit of a non-sequitur.
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've just hit the point where people are trying to do the same thing in a browser.
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? :)
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's also allowed developers to build useful applications that are immediately distributable to pretty much anyone who has an internet connection.