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

201–210 of 422 posts

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

#201

Post by mod »

andr3w321 wrote: post #98
robertfw wrote: post #77

Earlier quoted context omitted.

> All these frameworks end up creating much more problems than they solve. For small projects, sure, they might. But working at larger scale falls apart using plain html and jquery.

I assume by scale you mean many pages and not many visitors. For something like hackernews plain html and jquery would work perfectly fine.

Yeah, I didn't mean scaling to users.

Scale was a poor choice of words. Front-end complexity is a better metric, and in particular complexity which relies on manipulating state.

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

#202

Post by rtpg »

ng12 wrote: post #105
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…

Well what's unique about HN and Wikipedia? They're largely non-monezited. If Buzzfeed can make more money off of a flashy website it's hard to argue with.

HN doesn't do much, but Wikipedia does a decent amount of stuff with JS on their website despite people taking it as an example of "the web as documents"

meanwhile, I don't know how FB or Twitter are nice user experiences when you operate on a "paginate 20 tweets at a time" philosophy.

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

#203

Post by appleflaxen »

gkoberger wrote: post #153
nkkollaw wrote: post #124

See, Google should learn from Facebook: total API compatibility with the previous version. They saw what happened with Angular and Angular 2—which Google named the same despite it being a totally different framework—and made a smart move.

That's a luxury you only get when your API is good. With Angular, the problem was the API.

what does that have to do with whether or not to completely change the name of the re-write?

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

#204

Post by Simorgh »

avodonosov wrote: post #191
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…

I would love HN to provide an easy way to see where the reply thread to this first comment ends. Some js might enable that. Basic html/css - I think no.

It's that [-] button next to the username above each comment. It collapses all the cascading comments. It is enabled via JS. If you disable JS, then it disappears.

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

#205

Post by chillacy »

sharun wrote: post #184
metalliqaz wrote: post #36

Earlier quoted context omitted.

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…

It's like the Engineering teams at Google and Facebook have never heard of Microsoft or Sun or Adobe. There are so many lessons (learnt the hard way) in the evolution of .NET, Java and Flash that these guys seem to be completely oblivious too. Google, Facebook devs please go spend some time with the language and platform greybeards at Microsoft. EDIT: Feels like Software Engineering needs a set of Software History te…

Any specific examples? Nodejs seems like it's managed to avoid the early java mistakes of XML everywhere and one-thread-per-request servers.

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

#206

Post by chillacy »

mirsadm wrote: post #171
troncheadle wrote: post #149

Earlier quoted context omitted.

And I would love if my 2001 Honda Accord was compatible with Tesla's autopilot, but I understand it is not a realistic expectation. I'm not sure why you'd expect the web to be a. Mostly text and b. able to render easily on obsolete devices. The web is becoming a robust application delivery platform. That is so, so awesome. Most people do not want to be stuck with shitty looking, text only websites. Moving the platfor…

They may be robust but the user experience still sucks. JS heavy web sites are unresponsive and turn my 3 year old MBP into a vacuum cleaner. Facebook is the best example. I can barely load the web site without the fans spinning. Firefox can't handle it at all. It is unusable for me.

Might be more Firefox than your macbook or the web. I've noticed (while developing an extension) that Firefox feels noticeably more sluggish than Chrome. Safari somehow feels even faster than Chrome, but I'm too tied to the extension ecosystem of Chrome to switch.

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

#207

Post by madeofpalk »

Cacti wrote: post #81
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…

Huh? Who is talking about monoculture? OP certainly isn't, and I don't think anyone else is seriously suggesting such a thing. It's not unreasonable to expect that the ecosystem doesn't operate under an ever-expanding set of wrappers, frameworks, layers, and models, and it's certainly not unreasonable to expect that our tools don't suck. The open standards you talk about ARE already a part of the ecosystem, and well-…

First, let's be clear here: React was first open sourced in 2014, being used at Facebook extensively before that. Sure, it's no Win32 API, but it's not exactly the new kid on the block.

But the point of the web already having these standards is exactly the point - these frameworks are built on top of and contribute to the underlying universal standards, so what's the problem?

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

#208

Post by ww520 »

erikpukinskis wrote: post #188
red023 wrote: post #187

How does it compare with vue.js? I never worked with any modern JS framework like this but on paper I did not like writing CSS in javascript and vue.js had a normal way to write CSS and to me it looked superior in other ways as well.

What was your objection to writing CSS in JS? It would seem like a fairly trivial syntactic transition to go from one to the other? It's just selectors with a dictionary of properties right​?

It's another new proprietary syntax/api for CSS.

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

#209

Post by johnwheeler »

colordrops wrote: post #43
metalliqaz wrote: post #36

Earlier quoted context omitted.

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…

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…

People wouldn't complain about it so much if it didn't suck.

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

#210

Post by madeofpalk »

lobster_johnson wrote: post #143
davnicwil wrote: post #48

Earlier quoted context omitted.

Whoah, hang on, really? Do you have a source on this or somewhere I can find out more details? This will completey break a lot of libraries, components, etc that rely on the React lifecycle contracts.. Certainly doesn't feel like a small change! :-/

Fortunately, componentWillMount is largely made redundant by the use of constructors.

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
Post reply on HN