[andrewstuart2]

Additionally, if you have even 2000 data bindings onscreen at once, your users are likely going to be looking at too much information no matter how snappy your UI is. The more info your $watch has to deal with, the more info your users have to expect to change.

The more you want to throw on a page (say for infinite scrolling), not surprisingly, the more you'll have to be careful about how you do it. The benefit with Angular has always been that it brings the difficulty of every task down a notch or two and limits your cognitive load, very much due to its design. You still have to design your page and architect your data.

To be honest, after three years with the product, I still think Angular (1.x) was 10 years ahead of its time.

I've also come to a realization about Angular 2.0 as well: how many people are still using Windows XP? It's almost 4 versions behind, and closed-source to boot. I (as many others did) jumped all-too-quickly to the conclusion that I had to switch to version 2.0 when it came out. That's simply not the case.

Heck, even Microsoft seems to get every other version wrong. Maybe Angular 3.0 will be the time to switch.