Live data from Hacker News

Facebook Announces React Fiber, a Rewrite of Its React Framework

techcrunch.com

271–280 of 422 posts

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

#271

Earlier quoted context omitted.

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​?

Writing CSS in Javascript brings back memories of pre-2000 web development, table based layouts and more horribly inline styles inside HTML tags. CSS was a breath of fresh air, it meant separation of concerns.. HTML the content and CSS the visual representation. With the advent of jQuery it allowed separation of behavior as well. With frameworks like React these days, content+behavior is in JavaScript already, and wi…

I had this same initial reaction, but concluded as others have that this architectural approach was not actually a separation of concerns but merely an unwieldy separation of technologies: http://blog.andrewray.me/youre-missing-the-point-of-jsx/

When you start thinking in components it becomes much nicer to have the styling, logic and layout all in one file, isolated from the rest of the application and easy to edit, move around and apply to any page.

The previous 'best practice' of having these coupled aspects in separate files now seems quaint and tedious.

There are of course trade-offs, and CSS-in-JS has not triumphed yet, but if you've held off from considering this approach simply because you've had 'separation of technologies' drummed into you in the past you might be missing out.

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

#272
post #234

Earlier quoted context omitted.

Amen! React might be the best tool for building hybrid mobile or even cross platform electron apps, but the truth is, it suck balls for web development​. Bundling the entire website inside a single js file, that needs to be re-downloaded everytime you add a div or change a single css class is stupid, sorry. Your website doesn't need to be pure text. It can be beautiful, modern and responsive. And it doesn't need much…

React is great for web development (using Next.js) based on my recent experience. Citing only one side of any architectural trade-offs isn't particularly interesting either. The other side is that we can now easily build sites using Universal JS (serverside-rendered combined with SPA). Delivering a website with seemingly instantaneous repaints even on flaky internet connections is just a superior end-user experience.…

What has been your experience on server side rendering ? We are very concerned about SEO,etc - have you seen any impact of using Next.js on SEO performance,etc

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

#273
Everyone working on JavaScript right now lives in a bubble. Take a look at how back end languages have evolved and that's your future, you can try to deny it but your going to go the way C did and Java did. You can cite openness and the web and all these other things that make some kind of sense but history is against you.

In reality those arguments don't hold water. In reality our field is 30 years+ old and there is some maturity in the way things are done. All this crazy shit of rewrite everything all the time will just eventually tire people out and people will cut this redo an entire framework just because out.

JavaScript is one of the most important languages around right now and pretty soon the adults are going to be taking it away from the kids. Just as an FYI, this is another example of that. Too many important decisions are happening without much thought about what's there already.

I don't know maybe I'm wrong and maybe this time will be different but I've been around long enough. I learned the ins and outs of angular only to be told "fuck that" shortly after. It all seems very wrong too me but maybe you can tell me otherwise?

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

#274
post #7

> The company hasn’t previously talked about React Fiber Except, you know, the entire presentation on it at React Conf back in March.

They changed the article to "The company hasn’t previously talked MUCH about React Fiber" (emphasis is my own).

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

#275
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…

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…

> Increased resources availability and consumption over time is fairly consistent across most aspects consumer computing.

Worth remembering this is the case for people interested in tech. The local library still runs Vista on a 10yo system. My parents will use Android 2.x until the phone does not turn on anymore. Bandwidth updates don't apply to many people living outside of towns. Etc. It's been a long time since we've reached a point where an average person shouldn't need more bandwidth and power to look for information online.

And BTW​, you can have beautiful text-only websites. These 2 properties are not related.

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

#276
Neither the comments nor the article mention this, so I figure I'd ask here -- the React team has been promising performance improvements for stateless functional components (I think because they require less/no overhead + lifecycle management) for some time now, but I don't think it's moved beyond that.

Does Fiber introduce any of those optimizations, or nah?

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

#277
Anyone have a link to some benchmarks? As much as I enjoy the hype train sometimes, I'm not finding hard data on how much faster this is than the current React/Preact/Inferno .

So much hype and no words about performance... I'm wondering if it's slower.

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

#278

Earlier quoted context omitted.

Monocultures develop because of corporate backing. The web being open and unclaimed is what leads to the great diversity. As someone who does both server and JavaScript development, the tools are not bad. Often times they solve real problems well.

The web is pretty much corporate. All the major tools are built by major corporations, all the browsers are developed by major corporations (with the exception of Firefox, but Mozilla gets most of its money from major corporations) all the major web players are major corporations, all the major web monetization is rented by corporations. The web's no longer an open platform. Yeah you can put up a blog on your own ser…

Firefox started out as Netscape so you can trace it back to big company.

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

#279
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…

> Sure, it's bewildering right now, but in the future, this will all be knit together in a cohesive way.

You'll get over that optimism when 20 years passes and it's a worse mess than it is now; that's what going to happen.

Post reply on HN