Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook Announces React Fiber, a Rewrite of Its React Framework

techcrunch.com

Post reply on HN
Print view View original

331–340 of 422 posts

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#331

Post by julian_1 »

tannhaeuser wrote: post #315
julian_1 wrote: post #199

Earlier quoted context omitted.

No-one could even agree on making HTML5 valid XML - in order to leverage all the tools and knowledge that exist in that space. Not that I even like XML. But having another XML dialect that's not actual XML shows that the only hope is to build valid tools and abstractions on top of all the crud.

There's nothing "not actual XMLish" about HTML. HTML is formally describable in its entirety using SGML (see my project at http://sgmljs.net/blog/blog1701.html ), just not by the XML fragment of SGML.

Is it possible to scrape random html5 pages off of the internet and transform them with xslt 2?

Or write content/metadata schemas (distinct from a DTD schema that simply describes html5) using XSD?

Unlike xhtml, my understanding, was that the current tooling around XML won't just work out-of-the-box for html5.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#332

Post by bluesnowmonkey »

acjohnson55 wrote: post #144
paganel wrote: post #49

Earlier quoted context omitted.

Not the OP, but I expect the web to be a thing where documents (i.e. mainly text) don't have any issues rendering on my 5-year old phone or on my 8-year laptop (both of which work very well, still, and which I don't plan to replace anytime soon). The recent web practices (I'm talking mostly of the last 2-3 years, since more and more people have started copying Twitter with its launch of its "every website needs to be…

A web limited to textual content is a pretty quaint and uninspiring vision, IMO. The web started that way because static documents are relatively easy to represent, but the future (and present, for that matter) is rich experiences that can be distributed in the same way. But there are many steps left to get there, so either buckle up and help build that future, or get used to an ever-shrinking ecosystem of the purely…

You could say the same thing about flying cars. A car with four wheels is a pretty quaint and uninspiring vision, IMO. However it happens to be infinitely more practical.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#333

Post by roguecoder »

crusso wrote: post #213
kuon wrote: post #30

I've been working with react for a bit more than a year, and I am trying elm. I think elm is the best thing that happened to the web in general. It's really daunting at first, but I highly encourage you to try it.

Elm blows me away. It's everything I saw that React was trying to do, but bound up in an actual language that has strong Haskell-ish types, is fully functional, and mind-bendingly fun to learn. Elm really could be the future of bullet-proof web development. It has everything it needs except for runaway popularity.

"Mind-bending" being presented as a feature could possibly explain the lack of popularity.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#334

Post by cwyers »

julian_1 wrote: post #331
tannhaeuser wrote: post #315

Earlier quoted context omitted.

There's nothing "not actual XMLish" about HTML. HTML is formally describable in its entirety using SGML (see my project at http://sgmljs.net/blog/blog1701.html ), just not by the XML fragment of SGML.

Is it possible to scrape random html5 pages off of the internet and transform them with xslt 2? Or write content/metadata schemas (distinct from a DTD schema that simply describes html5) using XSD? Unlike xhtml, my understanding, was that the current tooling around XML won't just work out-of-the-box for html5.

You're missing the point. HTML wasn't XML because XML didn't exist then. SGML did. XML is a "an SGML dialect that's not actual SGML," not the other way around. The people who designed XML knew the SGML spec, as they wrote XML as a subset of it, and they knew what was in HTML. They could have written XML so that HTML conformed. They chose not to. But the HTML spec at the time was absolutely conformant SGML.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#335

Post by mathw »

toyg wrote: post #297
azernik wrote: post #217

Earlier quoted context omitted.

The success of the JavaScript stack was not dependent on source being shipped to the browser, and the push for WebAssembly​ is not motivated by keeping source away from the browser.

What? It absolutely was. Whole generations of today's JS people trained themselves with View Source.

That was before minification. I think that ship already sailed.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#336

Post by girishso »

kuon wrote: post #30

I've been working with react for a bit more than a year, and I am trying elm. I think elm is the best thing that happened to the web in general. It's really daunting at first, but I highly encourage you to try it.

Elm is amazing! If you have all the pieces in place aka model, view and update; once you get it compiled successfully.. it just works, it's mind blowing. This also makes refactoring a joy.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#337

Post by danabramov »

wayfarer2s wrote: post #265
madeofpalk wrote: post #210

Earlier quoted context omitted.

Except it's not for when you actually want to know when the component was put into the DOM, or you're running react server-side

> when you actually want to know when the component was put into the DOM You can use componentDidMount for that and its semantics are still the same.

Yes, componentDidMount is the place to work with DOM. componentWillMount never worked this way—it is basically a glorified constructor from pre-ES6 era.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#338

Post by weq »

metalliqaz wrote: post #36
acemarke wrote: post #11

I'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…

amen. I rolled a angular app 3 years ago, and now most of the libs i used are unsupported, and impossible to upgrade anything cause of dependency hell.

now we dont use yeoman to create react apps, and we have a thousand start kits that get u off the ground. your node_modules directory probably has 30k+ plus files before a single line of your app is written. yarn

just imagine ur an embedded programmer, and you boss asks u to write a hello world for the nexet device, and u come back with a react app with 30,000 dependencies to get the job done. then u find a bug, which fb just fixed in the next release. But u cant upgrade to the latest version, because that conflicts with library that is used by a 3rd level dep, that is used to add padding to a smiley somewhere.

Re: Facebook Announces React Fiber, a Rewrite of Its React Framework

#340

Post by danabramov »

b34r wrote: post #220
cheapsteak wrote: post #132

Earlier quoted context omitted.

Not sure if serious, but this update swaps out the internals without affecting users/developers, the API is fully backwards compatible

It's actually not. There are some lifecycle changes, potential modifications to setState (async only), etc. That's why it's being released as a new major version.

setState is not async-only in React 16. We keep the old behavior and just change the engine now. Later we will look into enabling new behavior.
Post reply on HN