Thats exactly what you DONT want to do. "hold out, use angular for the time being" Once 2.0's released we can all just spend the next 6 months rewriting our entire application so it works again!

I disagree with pretty much everything you've said here!

I think you should look at a timeframe also. If you write an application today in Angular 1.x you could probably contiue to use it for about 18-24 months. It is really hard to know which frameworks will still be maintained in 24 months time and it is not unheard of rewriting the application anyway after that time. As for the actual rewrite from Angular 1.x to 2.x I think Google will create scripts that help with the rewrite making it go much faster than 6 months. They actually have a LOT of internal applications written in Angular 1.x and would probably not want to spend the whole of 2016 rewriting everything.

You just reminded me of the Python 2.x -> Python 3.x "migration"

Yeah, there's a striking similarity between the two. Luckily though, Angular is just a framework, not a full programming language.

even if you don't have to use AtScript to write your app you will still need to know it to understand examples. This will make it mandatory to learn for most intents and purposes.

Agreed. It seems like it's primary purpose is to add dependency injection annotations, so its similar to today needing to understand `['$q', function($q) {` notation, or the special `$get` function for providers.