We use Angular on our application and I can't stand it. The only thing I like about it is how well testing is built in to the framework. Beyond that it is far too complicated. Once your project really grows and you've got a huge Angular codebase, with the sometimes inevitable rushed pace you need to work in at a company, it just becomes a disaster. "Scope" crap everywhere that you have no idea where to find what you're looking for.
Definitely would look into something else for my next project.
> "Scope" crap everywhere that you have no idea where to find what you're looking for.
A framework can't stop people from writing bad code. With Angular (or any other framework) you need to build the object model independent from the controller and template. The dependency injection makes this really easy. Then you've got logic that can be tested in plain unit tests and only a couple objects assigned to the scope (the roots of larger object graphs).
This is what I've run into on every Angular project I've been thrusted into. It goes from a somewhat decent separation to absolute chaos incredibly quickly. While that's the developer's fault I don't feel like Angular lends itself to extending and revising existing applications very easily.
Definitely would look into something else for my next project.