I think Angular is actually great for productivity, with the limiting factor being performance. Certainly, the initial learning curve can be painful, but after that I believe productivity is one of its strong points.
I’m trying to think about what part you think is 10x more lines of code than it should be and my best guess is directives. While directives can initially seem painful, if done right, they are perhaps the best part of Angular (along with 2 way data binding - ignoring the performance liability).
Certainly anything can be overdone or done poorly, so those may be factors. However, directives help turn HTML into your own enhanceable DSL with logic encapsulated in a new element.
Downsides of directives are one, the logic can flow from code to markup to code, which initially can be confusing and two, the setup required to create one. Perhaps I’m an Angular heretic, but I think avoiding excessive directives with a little jQuery in the controller isn’t always bad, especially when the code is still taking shape.
Other than directives, I’m not sure what part would be the 10x increase. Services don’t seem much different from utilities. Controllers or views? Our team must be somewhere around 1 million lines of Angular code and I think things are holding up well with productivity fairly strong. The primary issue I’d say we are seeing is regarding watchers and performance. It’s easy to let the number of watchers get out of control, but it's not that bad and only in areas where users can create 100s of custom widgets.