In the middle of this months, Google announced the Angular 2.0 at a meet up event in one of its Mountain View offices. I was lucky to hear the announcement on site and asked a couple of questions. That was truly exciting news as I had followed up the Angular 2 for a while.
Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.
Like any other software, Angular evolves over time mostly with incremental changes. The Angular 2 is, however, a very big jump. It’s fair to say that the only unchanged is the name itself. The disruptive changes break all the applications written for Angular 1. That is why quite some people consider Angular 2 is essentially a new framework. Whatever learned on Angular 1 is no longer applicable in Angular 2.
While Angular 2 comes for a good reason, it could be a pain for existing application developers. For existing applications to work with Angular 2, you got to re-write your application code. It may be possibel for Angular 1 and Angular 2 to co-exist and then migrate gradually. Getting it work may take lots of time as well.
Now, most people in the big Angular community start to wonder: should we move onto Angular 2 now? Is it possible to migrate all code? What is the cost of migration? These are not only technical questions, thus need broader evaluations. Let’s stay on the technical side.
For people who just came to the Angular community, the answer is easy: go for Angular 2 directly.
For people who have created applications already, the answer really depends for now. If you have small applications, migration probably takes not much time. If you have big applications which should get you the most out of migration, migration can also be costly and sometimes not possible.
So for us, we probably have to wait a little time for the 3rd party libraries finish migration, or we can find alternative libraries that are Angular 2 ready. I think there are many developers facing the same issue. Hopefully in a few months, the community will get marjority Angular 1 libraries migrated to Angular 2.
As a side note, while reading articles on Angular 2 migration, I find some are talking: since Angular 2 is essentially a different framework, why don’t we move onto yet another simpler framework called Aurelia? Haven’t done much homework but read a tutorial. It seems simple and elegant. But until digging into it deeply, it’s hard to conclude which is better for now. Maybe something I will do when I find time.