In the past years, more projects were developed in  Angular. Nowadays is the dominant front-end framework and Google didn’t pretend to lose this position without a fight. 21 months have passed since the announcement of Angular 2 and we are very close the arrival of the Beta version.


And, obvious, everyone start to question “Is it the time to start making my projects with Angular 2?”


To begin, the changes:

Angular 2 is not a usual update. The changes are so drastic that applications in Angular 1 will not be compatible. Syntax change, end of $scope, controller, and viewmodels, components become the center of the framework, AtScript to TypeScript, ECMA 6 is a must have and the possibility to develop a mobile app in a native way.


Some changes can please some developers, but the fact the Angular 1 applications are not compatible is a big issue for the community. After so many complaints, two initiatives emerge to help the transition, ngUpgrade and ngforward, but both require some work that is not welcome by developers.


What are  ngUpgrade e ngforward?

Both solutions are to help migration. ngUpgrade is the Google solution that let you run Angular 2 code at Angular 1. ngforward was created by the community and let you write code similar to Angular 2, but don’t use ng2.



Times have changed. Unlike the time that Angular.JS was released, the front-end framework market is more competitive now than ever.

JavaScript gained power during this period and others companies launched really good competitors. React.JS, by Facebook, Vue.JS e o Aurelia, created by Rob Eisenberg, part of the core team of Angular, just to say some.


Having spent so long in development, Angular 2 will allow your competitors to be more mature and the community with the propensity to exchange. After all, will be needed a good amount of work to make the updated Angular 1 to Angular 2 applications.


Should I use Angular 2 now?

A lot of applications actual needs are answered by Angular 1. If with thing enterprise applications, that just started using Angular 1 now, make this kind of migration is practically impossible.

  O grande fator que pesa contra o Angular 2 é a incompatibilidade com a versão anterior e a demora excessiva para o lançamento da nova versão.

The major factor against Angular 2 is the incompatibility with his older version and the delay of launch of the new one.

Angular 2 moment, even with beta version arrival, is to experiment. Learn how to use the new syntax and changes to seen what possibilities are open to now on. Be able to create native applications with Angular strategies is attractive but not sufficient to risk.  Applies to small and personal projects. Wait a little longer for the “new” framework get traction will not hurt.