Choosing Angular 1 Over Angular 2
February 9, 2017
That's right. You're reading this correctly. Angular 1 over Angular 2. Before we make the arguments for why sticking with Angular 1 may be the right choice, it's important to understand the current landscape of Angular.
Angular vs Angular 2: The Current Landscape
Angular 2 was just released in 2016. It is a complete rewrite of Angular 1 and addresses virtually every major pitfall experienced with the original. It does away with things like scopes and directives and takes a more component based approach (versus Angular 1's MVC).
Such improvements have many developers comparing Angular 2 to React.js instead. Forget Angular 1, it's now React we should be competing With it's flux architecture and change detection mechanism, Angular 2 does seem to give the highly regarded React.js a run for its money.
The Real Issue for Angular 1
To make a long story short, those that have come to love Angular 1 are starting to feel a bit forgotten. Not only has the framework been completely rewritten, it's also quickly becoming largely ignored as React.js and Angular 2 fight for the future of front end development. This makes it very hard to continue writing Angular 1, especially with its blatant issues that both aforementioned frameworks seem to have solved.
Don't Give Up On Angular 1
There's also thousands of developers currently using Angular 1. It's not going away anytime soon. Developers have become too familiar with Angular 1 to migrate existing code to a newly written framework. Such a rich community has also produced open source extensions, with thousands of custom modules/directives available for developers to improve existing pitfalls.