I worked at a startup that used angular. That was my impression also. It was taking them 3x-5x longer to implement features than what I thought was reasonable

I worked at a startup that used angular. That was my impression also. It was taking them 3x-5x longer to implement features than what I thought was reasonable. The CTO picked angular because he wanted to pad his resume with angular experience. The other programmers were to junior to notice they were running around in circles. That's actually a common anti-pattern for startup failure. The CTO makes a technology choice based on padding his resume, instead of technical merit. He's looking out for his future career at the expense of his current startup. There also were all sorts of weird performance issues with their website. If I left it running for an hour, it would crash. There were all sorts of weird "$digest in progress" errors in the console. I'm pretty sure they weren't using angular correctly. However, if a team of average programmers aren't using angular correctly, do you blame them or blame angular? Also, they were using angular 1.0, which means they're stuck now. I don't mention angular on my resume, because I don't want to work with angular.