The official advice (as well as my own) is to use Angular 1 for new projects until Angular 2 has been official released.
This is something that we intend to adhere to for our customer projects at work. However, we have found Angular 2 to be a mostly pleasant experience for working on our own internal utility software. We felt it was OK to risk the alpha/beta-ness of A2 since we are not putting anyone but ourselves on the hook for the applications support. I know of developers from other companies that are attempting to write an application slated for production in Q2/Q3 and they are writing it in A2. They have to come to a complete standstill in various development efforts because functionality was either not finished or simple doesn't exist yet. That being said A1 is still a great framework. While A2 leverages a lot of up and coming technologies to provide a better developer experience, A1 applications can still be written to take advantage of these benefits. I would strongly encourage taking a look at the A1 best practices guides, especially those that are written in reference to A2. An application written to take advantage of this advice should be fairly easy to port when it comes time. Lastly, other than the fact that 2.0 is being worked on, what is it about A1 that makes you say, "I don't see a point in going in that direction". Hope this helps. On Sunday, November 22, 2015 at 9:13:08 PM UTC-6, gitted wrote: > > Hi, > > I have an app that I want to launch in Q1 for 2016, can I start using > angularjs 2.0 today? > > I have been learning angular 1.0 for a while, but I don't see a point > going in that direction if 2.0 so close to being released. > > Thoughts? > -- 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.
