Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialYosef VanTine
8,880 PointsAngular 1 or 2
I was just going to start building a web app with Angular (https://angularjs.org). I went to the angular website and for the first time had a look at Angular 2 (https://angular.io). While I was doing Huston's course on angular 1 I didn't have any problem understanding angular as it appears many people do. I grasped it straight away so I am aware that they are very different and I don't have a problem taking the time to learn angular 2, but I want to know if it is worth it. I have looked around but haven't been able to find a recent article about whether it is to early to use Angular 2 in a live app or not. Any suggestions would be really appreciated! Huston if you have any thoughts I would love to hear them.
2 Answers
akak
29,445 PointsHi Yosef,
It's not too early to work in Angular 2, as long as you can spend some time refactoring code when something changes. In the past that was more true than now, since RC is out, but it can still change a bit. In the company I work for we have 2 project in Angular 2. Normal projects, not just test stuff.
But have in mind that clients are not yet very eager to have Angular 2 apps as it's still quite difficult to find developers that can work on that kind of code. And usually they prefer to have a code that if need arise they can give to someone else to fix. Just today I had a discussion with a client about a new small freelance project. For a moment he was leaning towards Angular 2, but then decided that we'll better stick to Angular 1 as it's safer after my work is done to give it to someone else if needed. I would prefer to go with ng2 as I'm quite confident with it at this point, and could use more practice, but well, Angular 1 it is. And I think in 2016 it will be still first choice for many companies. I think mastering it is still a very good skill, rather than knowing some of it, and some of Angular 2.
Also consider the fact that Angular 1.5 and up includes elements that allow similar way of building apps as in Angular 2. Component approach, lifecycle hooks, new router, all those things are similar to what you'll be later expanding with Angular 2. So maybe it's a nice idea to work with that for a while, and then move to Angular 2? But it's just a suggestion and some guesswork on my side, so don't take it as anything definite :)
Abraham Juliot
47,353 PointsH iYosef, here are a few articles/ resources:
Yosef VanTine
8,880 PointsYosef VanTine
8,880 PointsFrom what you've said I think I will go with Angular 1. Many of the scenario's I have are very similar to the one's you mentioned. As this project isn't a personal project I will be working on this project with other dev's in the coming months and it is going to be the foundation for a company that we've just launched I think 1 is the way to go for now. Thanks for your advice :)