Angular has it's ups and downs like every framework. One of the core issues with angular is maintainability imho. There are few best practices and almost no d

Angular has it's ups and downs like every framework. One of the core issues with angular is maintainability imho. There are few best practices and almost no documentation on proper project layout. You can also build an application any which way you please. Want state in your controller? Sounds good. Want to build an app with nothing but directives? Sure. Inline all your HTML into your directives? yes please. Hell, in theory you could build an entire site out of comments using 'M' type directives. Of course the code base will be a bit of a mess - but it still makes great eye candy. Another issue with angular is that you're frequently doing a deep dive into how angular is built. Want a recursive directive built in the compile phase? Uh oh, my screen locked up. Pass a '&' scope method into a nested directive? Hmm, does angular wrap that in a getParent()?? Do I need to double bind the parent callback using '=' in the nested call? There is WAY to much need to understand the compile and link phase. My unit tests for $q promises don't fire because they only resolve on a $digest cycle? Uh, how does that work again? It's a great attempt to build a front end MVC. It definitely speeds up development time and it enforces the IDEA of testing your javascript at a least (a concept foreign to most jquery developers). However, it's still miles from being an ideal front end framework imho.