I would just say "framework" instead of Angular. That said, it seems the real issues that frame works solve are those of teams who are unable or unwilling to e

I would just say "framework" instead of Angular. That said, it seems the real issues that frame works solve are those of teams who are unable or unwilling to establish their own set of coding standards and thus fall back on using some other team of dev's coding standards. I'm not saying that's a bad thing - I'm all for frameworks on the backend, and like I said above, I'm for (loose) frameworks on the frontend (backbone + underscore). I don't mind standards, but I'm against Angular becoming the standard because its not very good.