I tend to dive a lot into a source code when I am working with a library. You always have missing spots in documentation but you can actually know what's going on by reading the code. This is one of the reasons I am super comfortable with Backbone.<p>However I cannot comprehend Angular's source code on github. Can anyone give me pointers on where to start reading it and/or how it's organized?
The video tutorial mentioned[1] really is excellent, and it's recent too so it's not out of date.<p>[1] <a href="http://weblogs.asp.net/dwahlin/archive/2013/04/12/video-tutorial-angularjs-fundamentals-in-60-ish-minutes.aspx" rel="nofollow">http://weblogs.asp.net/dwahlin/archive/2013/04/12/video-tuto...</a><p>AngularJS' strict adherence to separation of concerns is definitely a breath of fresh air.
The first feedback I always heard from new angularjs developer is: "A completely different approach that I've seen before... it's so productive".<p>Great blog post :)
The more I use Angular, the more I love it. I like how it's really easy to get started with it. Just avoid writing your own directives right away, that's still the one part that is super confusing (although powerful).
Best video tutorials I've seen on AngularJS yet: <a href="http://egghead.io" rel="nofollow">http://egghead.io</a> -- find directives confusing? watch a couple two minute videos, and it'll fall into place.
I have been wondering if I should look into AngularJS but I'm a bit worried about it's future given Google also has Dart which seems to be competing with it, or am I wrong? We all know what Google is like when it comes to closing stuff down.
AngularJS definitely requires a higher level of CS competence. It's initial learning curve is quite high compared to most frameworks.<p>It is awesome sauce.