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

Is ReactJS really fast?

blog.500tech.com

Post reply on HN
Print view View original

111–120 of 191 posts

Re: Is ReactJS really fast?

#111

Post by TheCoelacanth »

JDDunn9 wrote: post #36

I think many of the "advantages" of ReactJS are just hype - Immutable data, one directional data flow are easier to learn, understand, harder to break etc. - This isn't anything new, these are just concepts taken from declarative programming. You could always have used those concepts in your JS. They aren't better/worse than imperative programming. That's like saying Haskell is better than C++. - Two-way binding crea…

> JSX breaks your IDE's error checking and line numbers in error messages (and not using JSX is a pain/verbose)

Source maps. Unless you aren't using any form of minification or bundling at all, you need them even if you aren't using JSX.

Re: Is ReactJS really fast?

#112

Post by mejari »

nogridbag wrote: post #59
Cshelton wrote: post #5

I don't use React for it's speed, I'm sure I can make anything using vanilla or ember, or whatever just as fast. It's the way it makes you think about things...the developers on my team are now much more productive. They can jump onto something another developer has been working on and see what each component is doing. It's the declarative nature of React and the way it makes developers think about how they compose t…

I was swept away by the React hype a bit. I tried to sell my team on React by stating many of the same points and eventually we decided to stick with our current JS framework: ExtJS. And I'm thankful I was overruled a bit. For our team and the types of applications we're building ExtJS simply makes much more sense. I've used React now for a simple web app and also a Chrome extension. For certain UIs scenarios like Fa…

We're in the process of migrating from ExtJS to React, and it is, to put it simply, awesome. Ext was great when we started because it gave us all these great out-of-the-box components to just mix and match and shove things together and get things out the door.

But relatively quickly (i.e. as soon as we wanted to make something look like it wasn't Ext, and you can always easily tell an Ext app) we ran into Ext's inflexibility. A huge percentage of our code now is finagling Ext over an entire file of code to do what would be a line and some css in any other framework.

I have had the exact opposite experience with "boilerplate", as I see Ext needing much more of it than React.

As a caveat; we are building extremely complex enterprise-level software, but even for the basic stuff if you want to do what Ext wants you to do you are golden. If you want anything a pixel different? Good luck.

Re: Is ReactJS really fast?

#113

Post by jhummel »

dmak wrote: post #82
aikah wrote: post #22

Earlier quoted context omitted.

> The basic premise seems to be that AngularJS can be just as performant as ReactJS if you do your homework and avoid common pitfalls of AngularJS. While AngularJS(1.x) is a bit faster now, your comment is a bit like saying Ruby can be equally fast to Java if one does it homework. AngularJS has architectural problems that can only be reduced if one doesn't use much of angular features(scopes,watches) inside directive…

> AngularJS has architectural problems that can only be reduced if one doesn't use much of angular features(scopes,watches) inside directives(which means writing components in pure js). That's an interesting piece of advice there. Could you go more into this?

We've found this out at one of my contracts. We've moved off of the typical $watch/$apply model for our directives and replaced it with a simple observable solution like Scheming (https://github.com/autoric/scheming). Our components are always watching attributes on our Scheming models, which are outside the digest cycle. It speeds things up, and is much nicer to work with IMO.

Re: Is ReactJS really fast?

#114

Post by mejari »

dmak wrote: post #85
davnn wrote: post #39

IMO Angular1 and React are so different in their approaches that it does not even make sense to compare them. If you want to base your application on a 'kind of' functional design with sane reasoning you should know what to use. With Angular2 the discussion will be more interesting, but as far as I know Angular2 is not quite production ready.

Which is why we compare results, and not their philosophies and methodologies. It's like comparing CPUs from AMD and Intel, they have different architectures, but to understand real world performances, we compare results.

Except ReactJS and Angular are not the same class of thing. It's more like comparing an Intel CPU and an AMD motherboard.

Re: Is ReactJS really fast?

#115

Post by grumblestumble »

bpicolo wrote: post #80
JDDunn9 wrote: post #36

I think many of the "advantages" of ReactJS are just hype - Immutable data, one directional data flow are easier to learn, understand, harder to break etc. - This isn't anything new, these are just concepts taken from declarative programming. You could always have used those concepts in your JS. They aren't better/worse than imperative programming. That's like saying Haskell is better than C++. - Two-way binding crea…

Routing, http, and models aren't hard problems. Blaming React for not being an entire MVC framework is silly. It's not designed to be, and there are any number of ways to solve that problem. Being able to use it with ANY different set of solutions for MC is especially good. I can use React for UI on top of old jQuery pages if I want to. I'm not forced to change my entire application to use it. Decoupling is a really,…

.. until you're building a problem that requires regular external security audits, and you have to keep up with all of the micro-libraries you're using and any security issues they may or may not have. The Angular team has been very responsive to any security issues that have come up, and you get so much for free by using the framework.

Re: Is ReactJS really fast?

#116

Post by ojr »

Akkuma wrote: post #48
JDDunn9 wrote: post #36

I think many of the "advantages" of ReactJS are just hype - Immutable data, one directional data flow are easier to learn, understand, harder to break etc. - This isn't anything new, these are just concepts taken from declarative programming. You could always have used those concepts in your JS. They aren't better/worse than imperative programming. That's like saying Haskell is better than C++. - Two-way binding crea…

The most interesting thing to me is that React's virtual dom implementation, according to http://vdom-benchmark.github.io/vdom-benchmark/ , is generally the slowest of the bunch. You could pretty much move to using anything else and have a faster vdom implementation and smaller library. Additionally, many out there are so similar to writing React that I don't see how using React is a win over the alternatives. In my…

React might be slower but it is more battle tested against multiple browsers than other vdom implementations, any vdom implementation might have to take performance hits to support older browsers like Internet Explorer 8

Re: Is ReactJS really fast?

#118

Post by woah »

Touche wrote: post #60
whoisthemachine wrote: post #4

The basic premise seems to be that AngularJS can be just as performant as ReactJS if you do your homework and avoid common pitfalls of AngularJS. I would argue that the beauty of ReactJS is that it doesn't have any gotchas. It's performant without needing a deep knowledge of the framework.

> I would argue that the beauty of ReactJS is that it doesn't have any gotchas. It's performant without needing a deep knowledge of the framework. shouldComponentUpdate is just as "deep" as this Angular optimization.

shouldComponentUpdate is generalizable across any type of component. The angular thing looked like something array specific.

Re: Is ReactJS really fast?

#119

Post by grumblestumble »

lhorie wrote: post #92

Pet peeve: Can we please stop blindly abusing `track by $index` without understanding it? The thing with `track by $index` that nobody talks about is that, like many of the workarounds in Angular, it's a footgun in disguise. Consider this: http://plnkr.co/edit/qKm7fYZFCkXHI5pkPMYL?p=preview and focus on the first input. Notice that the focus stays on the first input, instead of sticking with the value as it jumps aro…

This is absolutely a contrived example. $index is the equivalent to `var ctrl = angular.controller`, something that serves very well to communicate basic concepts but that you would never use in a real-world application. If you're dealing with server side data, your model should have a real unique key/id, and that is what you track by.

Re: Is ReactJS really fast?

#120

Post by grumblestumble »

megaman821 wrote: post #43
JDDunn9 wrote: post #36

I think many of the "advantages" of ReactJS are just hype - Immutable data, one directional data flow are easier to learn, understand, harder to break etc. - This isn't anything new, these are just concepts taken from declarative programming. You could always have used those concepts in your JS. They aren't better/worse than imperative programming. That's like saying Haskell is better than C++. - Two-way binding crea…

I don't tend to think ReactJS has many advantages, just differences. Angular 1.x is optimized around creating pages, where as React (and Angular 2.x) are optimized around creating small components. Angular 1.x uses two-way bindings by default and you can opt into one-way bindings. React essentially does the opposite. I have had infinite loops pop up in Angular, just by having floating point numbers that don't "settle…

one-time bindings are not the same thing as one-way bindings.
Post reply on HN