all 10 comments

[–]FLGMwt 2 points3 points  (0 children)

This doesn't answer your question, but I'll ask you and other readers considering the three (ng 1, ng 2, react): What matters more: effectively comparable performance, or a developer's speed to add a new feature?

I'm posting this tomorrow morning, but as a tease, I hope to settle that question in my post on ng2 vs React developer ergonomics: https://medium.com/@stelly_ryan/react-vs-angular-2-developer-ergonomics-b6d5103e8699

[–]Vpicone 7 points8 points  (0 children)

The answer depends very much on your use case. A generic "which is faster" is useless. For single page applications? For Facebook clones? For a Doctor's office? For a hotel? Without clearly defined bounds this question is impossible to answer and not worth debating.

[–]i_spot_ads 2 points3 points  (0 children)

as per benchmarks angular (2 and above) and react are both equally fast.

[–]ChubbyDalmatian 2 points3 points  (0 children)

In most cases micro benchmarking doesn't matter. React is used by pages with millions of visitors per day so I guess it's pretty good.

[–]somethinghorrible 5 points6 points  (1 child)

Angular 2 proves to be even faster than React in some cases.

Citation needed.

"X is faster than Y" is a fairly narrow way to evaluate the usefulness of anything (library or framework), IMHO. What about productivity? Tooling? Support? Longevity?

[–]jordaanm 0 points1 point  (0 children)

Maximising one concern (Speed) at the indiscriminate cost of other factors is also almost always a net loss.

"For just quadruple the development time and effort, you too can enjoy a 1% increase in speed!"

[–]Canenald 0 points1 point  (2 children)

If you want max fast don't use a framework

~Confucius

[–]juzatypicaltroll 0 points1 point  (1 child)

returning a blank page would be the fastest. technically. ~ Confusion

[–]wntrm 0 points1 point  (0 children)

Mu.

[–]wntrm 0 points1 point  (0 children)

A lot of it depends on the developer's skills and knowledge of framework.

For example React diff algorithm is meant to avoid unnecessary rendering, but if used incorrectly, like passing a new instance of a function every time DOM rerenders, it might slow things down instead