Pretty much only when its out of alpha. You can make the case that a beta release might be stable enough ( if you don't hack it, play within the lines and update frequently ), but I think it is still too early.
Nothing is stopping you from using Angular 1 and then incorporating 2 slowly over time, however. The router will be able to handle both angular versions, so you can use them side by side as you transition. On Tue, Sep 8, 2015 at 7:38 PM, Sumant <[email protected]> wrote: > Hi, > We are currently planning a new project to be released maybe in 4-5 > months. I really want to use Angular 2 for this project but I keep reading > not to use angular2 for production apps. > I also read that angular2 might be out of alpha by end of year. So is it > wise to start using angular 2 now for production app that will release in > 4-5 months? > I do understand the API is still in flux but I was thinking it is easier > to adjust angular2 app to API changes than to convert the app from angular > 1 to 2. > > So maybe the real question is when is it ok to start using angular2 for a > production app? > > thanks > > -- > 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. > -- 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.
