hassanzaheer_

You can find the detailed discussion in the HN link above, but to summarize my viewpoint on this:

1. It already has a much bigger and growing community than any of the new frameworks

2. It has backing/support of Google, when such a big company puts steam behind something than you can be sure it's not going to die out just like that, and will continue to grow and improve, no other framework other than ReactJS has such a portfolio

3. Third-party plugins/components, AngularJS already has some amazing libraries/plugins/directives built that one can easily plug into the project (this is by far greater than any other new frameworks coming out)

and one can go on...

Haven't used ReactJS much but it looks promising in solving the problems created by AngularJS for instance its push-and-pull mechanism for data binding is efficient than angular's 2-way binding using watches...

> React is just the V in MVC, Angular is / can be the rest.

that's why its more of a micro-framework, its pluggability with other frameworks makes it customisable according to the proj requirements

couldn't agree more on the Python example, I think one of the main agendas for the 2.0 release will be to make it more popular on mobile side of things (https://www.airport-parking-shop.co.uk/blog/built-app-2-week... is one such example though not from the core AngularJS team) for which they may have compromised backward compatibility infavour of performance.

and also do you think they'll continue with the 1.x releases? since so many developers have already invested time and effort on their webapps and shifting it to an entirely new framework (read release) is a major cost to pay..

True. And like any other framework one can work around the bad parts by developing custom solutions, but Angular's one of the main features are its two-way binding which also happens to create one of the biggest performance bottlenecks as the application scales up. This can be fixed easily (bindonce is just one example) though it leaves Angular with little value.

Actually it depends more on the time of development and project specs. For now I'll probably choose ReactJS.

If by the time Angular 2.0 is launched then I'll definitely give it a shot, it seems promising and is based on ECMA6 utilizing the new features provided by it will be a plus.

IMO AngularJS can be scaled _IF_ used with caution, though I won't recommend it unless one has a good experience with its core.

While most of the arguments presented in this article are somewhat valid but I hope with the release of Angular 2.0 majority of the issues will be addressed (though does it make sense to make such drastic changes in the upcoming is another debate and already taken care of at: https://news.ycombinator.com/item?id=8507632)

I'm currently working on a comparatively large webapp built in Angular and it was after about 7 months into the project that we started realising it's pitfalls, and it was very difficult to abandon it then.

So we worked it around by: 1) using one-way binding (or bindonce to be exact) to reduce watches 2) avoiding un-necessary $apply() and using $digest() carefully if required 3) using ng-boilerplate for scaffolding 4) defining our own style guides/coding conventions/design patterns to overcome Angular's bad parts 5) frequent code-reviews that made sure new team members are upto speed with the above techniques

luckily we haven't ran into much issues after that :)

I would really like to see a good javascript profiling tool in FF. Chrome has one but I think it can be improved upon.