Angular Blog

Since we are yet to see the first Angular2 release (almost there, but not yet); most Angular2 third-party resources may not provide the most up to date information, so the best place to learn Angular right now is really the official Angular documentation i.e. https://angular.io/ , because it is updated quite often.

1. If you are looking for a book to learn in a sequential way then ng-book is a good option. ng-book is updated regularly however it is not free.
https://www.ng-book.com/2/#features

2. New blog posts are also a great way to learn about certain Angular topics. Examples:

2(a): http://blog.thoughtram.io/categories/angular-2/

2(b): http://angularjs.blogspot.com/ (Has both Angular 1.x and 2.x articles, written by Angular core developers)

3. Learning by observing:

3(a): material2 is a library, being developed by the Angular team itself, that is based on Angular2 and is frequently updated to use the latest Angular2 version (currently RC5). I refer to the material2 source code to learn the best way to write my own Angular2 app and custom components: https://github.com/angular/material2/tree/master/src/lib

The way I chose in the past. Use a jobsite (in my case www.cwjobs.co.uk). Type in framework. Count number of jobs. If one is significantly bigger in the job market, this gives me more flexibility and job security going forward.

This has resulted in me going with AngularJS as there are 7-10 times the number of jobs advertised vs other frameworks.

My current role also uses typescript and was using it before the Ang 2 announcement. I do watch where the various technologies are going within the whole stack.

I also find articles like this interesting as they show movements in the technology stack that I should be aware of http://angularjs.blogspot.co.uk/2015/09/angular-2-survey-results.html

I am currently using grunt, but feel I need to get into gulp.

The issue with Angular in extensions has to do with the fact it uses eval on the page DOM, which is controlled by the webpage. The webpage can put code into the DOM, and then let Angular execute it from within the higher-privileged extension.

Angular <1.6 had a sandbox feature which blacklisted specific attacks like this, but was not a general solution and was specifically not intended as a security feature. They entirely removed the sandbox in 1.6 because people kept thinking it was a security feature: http://angularjs.blogspot.com/2016/09/angular-16-expression-sandbox-removal.html

I'm not going to fault someone for not reporting a specific vulnerability with a specifically not-security feature that has already been removed.

> Is there any differentiation between the two on API stability?

Compare http://angularjs.blogspot.co.il/2014/10/ng-europe-angular-13-and-beyond.html

> Our goal with Angular 2 is to make the best possible set of tools for building web apps not constrained by maintaining backwards compatibility with existing APIs

vs https://github.com/emberjs/rfcs/pull/15

> This is not a big-bang rewrite; we will continue development on the master branch, and roll out changes incrementally on the 1.x release train. The 2.0.0 release will simply remove features that have been deprecated between now and then. Our goal is that you can move your Ember app to 2.0 incrementally, one sprint at a time.

Angular 2 to Angular 4 is not a good example of getting comfortable using something then the next version coming out. They are the same framework and it is trivial to upgrade Angular 2 to Angular 4. "Updating to 4 is as easy as updating your Angular dependencies to the latest version, and double checking if you want animations. This will work for most use cases." from https://angularjs.blogspot.com/2017/03/angular-400-now-available.html

Angular 1 to Angular 2/4 is a valid argument though.

There's more info on future plans here:
https://angularjs.blogspot.com.au/2016/09/angular2-final.html

Specifically:

> Bug fixes and non-breaking features for APIs marked as stable
> More guides and live examples specific to your use cases
> More work on animations
> Angular Material 2
> Moving WebWorkers out of experimental
> More features and more languages for Angular Universal
> Even more speed and payload size improvements

And immediately:

> Semantic Versioning