Hi Sander,

Thank you very much for your reply!!! 

On Friday, May 20, 2016 at 5:00:44 AM UTC+2, Sander Elias wrote:
>
> Hi Matheus,
>
> Angular 2 as a release candidate is pretty stable, so it could be used in 
> production. (there are some big sites in production with it already)
>
> However, the answer to the question lies more in the skillset of you and 
> your team. While angular itself is (sort of) ready, much of the tools 
> aren't. Also, the ecosystem is nothing compared to NG1. So if you are 
> dependent on 3rth party add-ons, the answer will be no. If you are capable 
> to fill in the blanks yourself, the answer is yes.
> The conceptual switch from NG1 to NG2 is not that big. That is not where 
> the main problem is. 
> However, NG2 is much more dependent on tooling. You need to get your 
> tooling right for development, and for deployment. At the moment my biggest 
> problem is that when I go back to an NG2 project, it takes at least half a 
> day to get the tooling up and running again. If you have left  the project 
> unattended for more as a week, you need to update almost all dependencies. 
> Be prepared to handle those issues. You will run into situation that 
> webpack requires X to be version Y, while something else refuses to work 
> with that exact version.
> All of it is solvable, but for me, way outside the 'fun' part of a project.
>
> Some of the stuff you need, and this is just to get NG2 going inside a 
> browser:
>
>    - typescript. (despite this seems optional, in my personal opinion 
>    it's not!)
>    - a tool that handles ES6 import/export. (webpack,systemJS,TS,...)
>    - task runner (gulp/grunt/broccoli/...)
>    - testing stuff (karma + jasmine seems obvious, but you might want 
>    something else)
>    - a lot of patience. (building and loading your app in the browser 
>    will take time)
>
> Typescript is a no brainer. To be able to utilize NG2 the way it's 
> intended, you need decorators. For now TS is the the solution there. Every 
> other line in the list needs careful consideration, and no matter what you 
> choose, everything there will occasionally play up, and will cost you time, 
> you can't use to 'just build' on your app. 
>
> Hope this helps you a bit,
> Regards
> Sander
>
>  
>
>

-- 
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 https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to