Hacker News Reader

Angular 1 is NOT Angular 2 or higher.

Angular 1 and Angular 2+ are in essence completely different frameworks.

The "Angular" team should have picked a different name for their post-Angular 1 project.

The vibrant ecosystem of custom directives, etc., that surrounded Angular 1 must NOT be confused with the Angular 2+ project just so that everything can be "one big happy Angular".

View on HN

But as i understand there is a workable update-path ( also automated client? Experiences anyone ) - and as far as i am just starting working with angular2 the general concepts are still pretty close to angular1. I stopped developing ng1 about two years ago, because i ran into concerns i couldn't fix - ultimatly breaking my use-case. But all of them are fixed in ng2, so i will give it another run ( with high hopes )...

They probably didn't want to feed into Google's reputation for abandoning their stuff, so they kept the same name to make it seem like a continuation of the framework that's been around since 2010. It gives the illusion of stability, even though it's actually the opposite.

"How can you not choose Angular? It's backed by Google and it's been around longer than both Ember and React."

Reply on news.ycombinator.com