As it takes some time to get into a new framework (not only scratch the 
surface) I would say, stay with what you are unless you are sure that 
Angular 1.3 is that much better for your case. Otherwise: if you are 
writing good code in Angular much of it will end in a data framework 
(angular-data?) and services. So even a completely new framework with a 
missleading name (Angular 2.0) should not lead to a complete code rewriting.
And as for ANY framework, I would not use a completely new version for at 
least one year - so the time to stick to 1.3 will probably be longer for 
most "real" projects. Can't tell my customers that nothing will be working 
for months because nobody has experience, nobody uses it, ... ;)

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to