Yeah, he had a few minor incorrect details - the $q one was a big omission, it sounds like he never explored using $q.all, much less $q at all.
I think Angular's complexity can be daunting without someone who can help set you back on the right path when you're stumped. We (the regular denizens on IRC) do a pretty good job in #angularjs on Freenode helping people out when we can, but it's obviously whenever people can spare the time to answer questions. I am constantly helping people at work grasp how to think the Angular way, and it has resulted in my team being incredibly productive due to Angular's excellent upsides.
Regardless though, I think it's good that this article was written, even if a little prematurely. People should know both the upsides and downsides.
I think Angular's complexity can be daunting without someone who can help set you back on the right path when you're stumped. We (the regular denizens on IRC) do a pretty good job in #angularjs on Freenode helping people out when we can, but it's obviously whenever people can spare the time to answer questions. I am constantly helping people at work grasp how to think the Angular way, and it has resulted in my team being incredibly productive due to Angular's excellent upsides.
Regardless though, I think it's good that this article was written, even if a little prematurely. People should know both the upsides and downsides.