Facebook Announces React Fiber, a Rewrite of Its React Framework

Post by ZenoArrow » Wed, Apr 19, 2017, 5:15 PM UTC

cubano wrote: post #172

ZenoArrow wrote: post #94

Earlier quoted context omitted.

>"At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative." You mean like Dart? Besides, languages that target WebAssembly are almost certainly going to evolve to fit that space.

I have serious doubts that WebAssembly is really going to come to dominate the web the way many people here seem to believe it will. The idea that all of sudden there is going to be a rush to push compiled/closed sites after so many very successful years of using free-and-open stacks seems rather non-logical to me. Time will tell.

Post by ng12 » Wed, Apr 19, 2017, 5:21 PM UTC

fauigerzigerk wrote: post #400

jakelazaroff wrote: post #387

Earlier quoted context omitted.

> Sure, but the patterns you use with the class syntax are incompatible with the patterns you use when using object literals How so? You can still access the prototype. It's just that the most common reason to — declaring instance methods — can be accomplished with the easier-to-read class syntax now. > Even with arrow functions, `function` still exists ands is more frequently used. ES6 is a non-breaking change. You…

>You can use arrow functions for literally every function you write other than generators But not for every function I read, and that is the problem with all backward compatible fixes to programming languages. You're just piling on more (sometimes better) features on top of all the old brokenness and everybody has to know all of it.

Post by antjanus » Wed, Apr 19, 2017, 6:47 PM UTC

cheapsteak wrote: post #250

b34r wrote: post #220

Earlier quoted context omitted.

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.

I think we may be splitting hairs over the definition of API compatibility

Post by jakelazaroff » Wed, Apr 19, 2017, 7:21 PM UTC

fauigerzigerk wrote: post #400

jakelazaroff wrote: post #387

Earlier quoted context omitted.

> Sure, but the patterns you use with the class syntax are incompatible with the patterns you use when using object literals How so? You can still access the prototype. It's just that the most common reason to — declaring instance methods — can be accomplished with the easier-to-read class syntax now. > Even with arrow functions, `function` still exists ands is more frequently used. ES6 is a non-breaking change. You…

>You can use arrow functions for literally every function you write other than generators But not for every function I read, and that is the problem with all backward compatible fixes to programming languages. You're just piling on more (sometimes better) features on top of all the old brokenness and everybody has to know all of it.

Post by colordrops » Wed, Apr 19, 2017, 10:58 PM UTC

dang wrote: post #323

colordrops wrote: post #43

Earlier quoted context omitted.

I don't know about others but I tire of these comments chiding the "out of control" front-end ecosystem. The situation has already changed years ago. We aren't going to get off of your lawn while you continue to beat a dead horse. The web is built on open standards and there are billions of pages and apps out there. To expect web development to be a perfect monoculture is a failure of your imagination and ability to…

I get the Javascript fatigue fatigue part, but this comment breaks the HN guideline against name-calling in arguments, and even crosses into incivility: > We aren't going to get off of your lawn while you continue to beat a dead horse. > a failure of your imagination and ability to adapt Please don't do this in HN comments regardless of how tired you are.