Quote:
Originally Posted by suzzer99
We may be switching from backbone to angular for our new responsive site.
Fwiw this guy seems to be a better resource on angular than actual documentation: http://www.egghead.io/
We've just about finished rewriting our main web application in AngularJS + ASP.NET MVC, (using iframes to backport some of the old functionality that's yet to be ported) and had great experience. The trickiest part was supporting IE8 with good performance, because it's so much slower than IE9+, Chrome and Firefox, which means a lot of components had to be rewritten when we realized our approach was too slow for IE8 and we had to write custom directives that remove functionality from built-in directives to run faster. And getting other developers to buy into the Angular way of things and imposing overall discipline have been tricky at times - some developers, especially those who are largely used to server-side apps with javascript/jQuery to glue together effects without having to deal with a large javascript code base, tend to write some cringeworthy, globally impactful hacks in Javascript/jQuery, which still somehow works with AngularJS, but are strongly against the spirit of how to do things in AngularJS and eat away at the benefits of AngularJS (code organization, separation of concerns, testability, etc).
I found it easy to embrace the AngularJS way of doing things, in part because I had no jQuery/javascript experience/baggage/preconception and being the person who introduced AngularJS to the team, got it accepted and led the project, I had a much stronger incentive to do it the right way. YMMV.