The force multiplication for most cases is intense. If you're doing something that looks like something lots of people do, then you're going to have a good time. That's the same deal with Rails.
Typically, the issues that people talk about surround the fact that in Angular, the one right way to do stuff hasn't been discovered yet. The fact that the way that Angular works is a pretty fundamental change from the way that webpages have worked for most of their history means that there isn't really much to go on. The patterns are still being discovered.
The situation isn't helped by the fact that lots of people dove into the ecosystem and started writing blog posts about how do do things with Angular.js without first learning why just using a directive to apply jQuery plugins is probably not the right approach.
Generally speaking, the problem is not that it's hard to think of a way to accomplish what you want, it's that it's hard to figure out what the Angular way is (usually because there is not one way, yet).