Angular 2.0 questions answered by the Angular team

gistfile1.txt

What is the release date for 2.0?

No exact release date yet. They don't want what happened with 1.2.They want to 
make sure they get it done right for 2.0 so they are not setting a date yet.


What is the plan for having a migration path for 2.0? How much rewriting of 1.x 
apps will need to be done to migrate to 2.0?

Mishko said that there will definitely be a migration plan for 2.0. They dont know 
yet what they will look like since 2.0 doesnt exist yet, but there will be one. 
And most likely tools to help with migrating. There will likely not be much code 
rewriting to do either so not to worry about that.


What was the reason for going with AtScript?

The reason for AtScript is to give developers better expressivity of intent. For 
that you need two parts:
1) some form of declarative metadata [annotations] and
2) a way of getting hold of the metadata at runtime [introspection]. 

see: https://docs.google.com/document/d/11YUzC-1d0V1-Q3V0fQ7KSit97HnZoKVygDxpWzEYW0U/

Currently no JavaScript(like) language supports the above, which is why we chosen 
to extend ES6 to give developers the expressivity which they need. 

The fact that we can use it to transpile Dart is nice to have, but it is not the driving force.

 
Will there be incremental releases 1.4+ - 2.0?

There will be beta releases but there will likely not be 1.5/6/7 etc.
Possibly a 1.4 but they aren't sure yet. They are planning to pull the router 
from 2.0 into 1.3x. They're still putting things out there early for people to 
get feedback on it early so they can make sure they move in the right direction.


Server side stuff... (not my question)

There were modules being described by Igor and Misko that will be reusable on 
the server, but they don't believe that there is a plan to allow whole 
applications to run on the server - they spent some time last year trying to 
support server-side pre-rendering. But in the end it did not get used so it 
was canned with the focus moving to improving client-side performance.


I think this clears up any fears or concerns I had for the future of angular.