The couple of times I've worked with angular, some things went incredibly smoothly, and when you hit those edges, it really reminded me of ASP.Net 1.0, it was nice for about 80% of your workload, but the other 20% took 10x the effort, and was a much bigger headache to work around.
Honestly, if/when browsers have better support, I think something closer to Polymer may be the best of all worlds with web development... for now, I find that React code tends to be the most sensible (with a decent framework around it)... not to mention shared client-server code with node/io.js
The most ironic thing in all this is that your comment is still full of Herd mentality, except that it goes the other way.
Angular is a framework, period. Using it is neither a good or a bad idea, it all depends on the people who actually use it.