Can I start using angular 2.0 today?

[gitted]

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?

[Donald Spears]

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.

[GeekOwl]

Hi,

I think Me and gitted are on the same page. I along with my teammates  have written a fair amount of code for our upcoming app. But its front-end is in a shabby condition. Being a startup we are working hard to keep abreast of latest technologies, giving our app a modern outlook. So keeping our back-end unchanged we are looking forward to re-writing our code and integrating either Angular 1 or 2. We also intend to launch it in Q2/Q3 of 2016. I have your point to follow A1 best practices guide and easy to port method from A1 to A2. But what are those best practices can you please give a link/ reference of your advice.


Thanks

[Sander Elias]

Hi,

Well, There are a couple of things you can do. Let me first quote from the official blog

What can I do today to prepare myself for the migration?
Follow the best practices and build your application using components and services in Angular 1 as described in theAngularJS Style Guide. 

Read the styleguide! that's already a lot of it. Then stop using $scope, and ngController (or, if you are starting, don't start using them. that's easier!) 

Also, you might look at ng-forward. that enables angular 2 (like) syntax for NG1. 

I know it's tempting to go NG2 from the start on, however, you have to realize it's still in alpha. There will be breaking changes. (Yeah, I know, google has already put out public projects on NG2, but then I ask you this, do you have the core team on call? And can you afford a major rewrite a few months in? I mean, do you have the manpower and money to do that?)

Does that help you a bit?

Regards

Sander

[Donald Spears]

In addition to following the style guide there are plenty of blogs about writing angular 1 code using Typescript. Taking advantage of Typescript now will remove yet another layer of complexity when switching to A2. I'll provide some links later when I have more time.

--
You received this message because you are subscribed to a topic in the Google Groups "AngularJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/angular/ypkCQhstmw0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to angular+u...@googlegroups.com.
To post to this group, send email to ang...@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

[gitted]

Say A2 gets released with a version 1.0 in Q1, it will then take time for other libraries like say Bootstrap UI to get converted to probably Q4 before things are really stable right?