I don't think it does have a steep learning curve, really. I first tried it when I was a real greenhorn, having played around with backbone and ember and not re

I don't think it does have a steep learning curve, really. I first tried it when I was a real greenhorn, having played around with backbone and ember and not really enjoyed the experience; with Angular you can be doing something cool in about 10 minutes. The weird terminology almost helps, especially if you're coming from a server-framework background where your Ms, Vs and Cs are pretty different (due to the difference between request/response and UI design) from the same terms in a client-side framework. I am not going to confuse $scope with an ActiveRecord model. Most of it, in any case, works a bit like this (or did for me when I was very junior) - 'if it has a dollar in front of it, it does Magic Stuff with little or no human intervention. No, the learning curve is very flat - until, as the OP says, you hit a brick wall. All that said, IME it is possible to properly organise code in an Angular app, get logic out of views and so on. But it is dependent on you knowing a bit about application design. The easy option is to turn scope into a god object and have a 500 line spaghetti controller.