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

411–420 of 422 posts

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

#411

Post by fenomas »

monkmartinez wrote: post #394
fenomas wrote: post #317

Earlier quoted context omitted.

> If it wasn't a problem, it wouldn't be upvoted. It's upvoted because it's HN's current favorite holy war. "Front-end development is out of control" is something everyone has an opinion about, in a way that the announcement of React Fiber isn't. That doesn't mean the same debate needs to be re-litigated every two days. Occasionally would be fine, but when it happens in every tangentially related thread it sucks the…

Because it is out of control! You have to have some serious "nalgas" to dive in... I tried some years back and said; "F this" I am going to learn Python and Java. I am not even paid to program in most cases. There is a LOT to be said about stability. It does need to be reignited or it wouldn't be. It is like being a climate change denier at a climate conference. "Uhhggg why are we talking about this again?" I don't b…

"Look, I know it's an off-topic rant, but this issue is so important than it warrants off-topic rants!", said everyone who's ever posted an off-topic rant.

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

#412

Post by kuon »

roguecoder wrote: post #333
crusso wrote: post #213

Earlier quoted context omitted.

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.

I dismissed elm about 10 times. But once I tried it, it was great. The pure functional approach of elm is like solving an equation. Once it is solved, it's done, you can go home. In the sense of that you write elm code only once, if it work, it will always work. And if it doesn't work, it won't compile anyway.

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

#413

Post by fulafel »

vertex-four wrote: post #388
fulafel wrote: post #306

Earlier quoted context omitted.

> We all switched from coffescript to ES6 and Babel because ES6, being standards-based, will eventually be supported in browsers, right? No, a lot of us switched to ClojureScript, TypeScript, Elm, etc and don't look back. As long as you have to transpile, why not transpile from a good language? (Not to say that native ES6 support would compensate for the advantages of the abovementioned languages) Standards are not g…

Or, you know, allow multiple implementations without someone having to reverse-engineer what's meant to happen in edge cases from the reference implementation...

In PL context standard usually implies a committee design, whereas language specification is used to mean an engineered formal definition to define semantics. I agree having a spec without the committee design is a mostly good thing.

Though there's a good argument for just blessing the most popular implementation as "the spec". Paper specs have bugs too, and they always live in a kind of shadow world vs real life.

Things that aren't theoretically specified are relied upon in real life. See eg the Java and C standards. In Java's case nobody cares what the standard is, all implementations just have to be Sun compatible realistically. In C's case it's really opened a world of hurt with all the undefined behaviour and resulting security problems etc.

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

#415

Post by jazoom »

danabramov wrote: post #343
roguecoder wrote: post #329

Earlier quoted context omitted.

Vue is much, much faster to load; it is possible to use vue applications over 3G where React apps choke. Vue is also, in my experience, much easier for back-end developers to contribute to without making app-braking performance mistakes. It has a canonical event-driven store, Vuex, with much nicer debugging tools than any of the flux frameworks (it includes getter values, for example). I have also found the error mes…

>I have also found the error messages more meaningful across the ecosystem; React can sometimes produce very unhelpful errors. Can you file an issue next time? We're happy to fix confusing errors. >much, much faster to load I would love to see some data backing it up. I thought they are roughly in the same ballpark with Vue having slightly more built-in APIs but I might be wrong!

I switched my complex app from React to Vue and the speed difference wasn't really noticable. Also, React had far better error messages. Vue's are often useless. This is actually the only thing I miss about React. Vue has been a better experience in every other way.

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

#416

Post by quickben »

colordrops wrote: post #325
quickben wrote: post #240

Earlier quoted context omitted.

It won't change the fact that a lightweight scripting language is coerced into running increasingly heavier apps. Defending it, comes off as a Stockhilm syndrome really.

What does "lightweight scripting language" mean? So much hand waving in this thread. ES6 is an advanced programming language rivaling most others and JS VMs are some of the most optimized runtimes in existence.

https://en.m.wikipedia.org/wiki/Scripting_language

Arguing grammar and references to adoption rates just illustrates the rest.

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

#417

Post by newsat13 »

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…

About self-hosted app architectures, Cloudron is really good in terms of stability. Just got a newsletter from them that they are hitting 1.0 soon.

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

#418

Post by cutler »

fulafel wrote: post #306
segphault wrote: post #101

Earlier quoted context omitted.

> And the other great thing about these tools is you can add/remove them as needed. In order to get that freedom, you need to build the tooling in such a way that it aligns with the web standards, so that when the standards catch up you can drop what you don't actually need anymore. We all switched from coffescript to ES6 and Babel because ES6, being standards-based, will eventually be supported in browsers, right? A…

> We all switched from coffescript to ES6 and Babel because ES6, being standards-based, will eventually be supported in browsers, right? No, a lot of us switched to ClojureScript, TypeScript, Elm, etc and don't look back. As long as you have to transpile, why not transpile from a good language? (Not to say that native ES6 support would compensate for the advantages of the abovementioned languages) Standards are not g…

Like Python? Sorry. Couldn't resist.

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

#419

Post by jpk »

bigato wrote: post #369
jpk wrote: post #97

Earlier quoted context omitted.

It won't happen because none of them will implement the other guy's new thing. Chrome would do the Google thing, Edge would do the Microsoft thing, and Firefox would sit back and balk that none of that junk is standardized. Then webdevs would just stick with Javascript and friends because it's the only thing that mostly works everywhere. That's exactly what happened to Dart, right? It had aspirations of hopping into…

Not true, see webassembly.

The parent and grandparent were talking about unilaterally developed tech, "At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative." etc

The correct comparison there is Dart. WebAssembly is a joint effort being developed by a team comprised of folks from every major browser vendor, so it isn't really an example of what they're talking about.

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

#420

Post by dkarl »

ehnto wrote: post #293
dkarl wrote: post #104

Earlier quoted context omitted.

God, that page makes me want to drop everything and work to make tests pass. My team needs that.

Yay my tests pass. Wait, what were we building again?

A web page to show our unit test results. I forget why.
Post reply on HN