4 ms·
From the giant table-as-JPG: | metric | AngularJS | React | |--------|-----------|-------| | speed* | 1.35s | 310ms | -* "based on loading 150
by danso 10y ago
From the giant table-as-JPG:
| metric | AngularJS | React |
|--------|-----------|-------|
| speed* | 1.35s | 310ms |
-* "based on loading 1500 rows [according to some 2014 blogpost]
Also, the OP recommends AngularJS for "Experienced developers and coders", while React is for "Casual developers and designers"
edit:
The narrative text is not much better. This sounds like something generated by a Markov chain:
> I’ll just mention that “one-way binding” in AngularJS 2.x and in ReactJS isn’t the same thing. The binding mechanism is completely different. It provides wider functionality in AngularJS 2.x compared to ReactJS. We’ll have to wait and see how it works in AngularJS 2.x. In ReactJS, the one way rendering flow is very straightforward, fast and easy to understand, debug and trace in comparison to “two-way binding” implemented in AngularJS 1.x.
- Shengbo 10y ago>Also, the OP recommends AngularJS for "Experienced developers and coders", while React is for "Casual developers and designers" Yea, I'd like the author to explain why.
- ruslan_talpa 10y agoseems like FB is full of Casual developers and designers :)
- sgk284 10y agoHe's trying to force a narrative, likely to justify his own personal choices of technology.
- ben_jones 10y agoI'd love to see the percentage of AngularJS or ReactJS applications that actually render 1500+ rows at a time. I feel like we're benchmarking (and talking about) the wrong things.