Because writing controllers, services, directives, etc. with various dependencies is something you do all the time, and the DI reflection lets you do so in a qu

Because writing controllers, services, directives, etc. with various dependencies is something you do all the time, and the DI reflection lets you do so in a quicker, friendlier, and non-duplicated way, whereas setting up the ng-min step is something you only have to do once, then you can forget about it. You already need to set up a build pipeline to get your minification, concatenation, etc. in the first place. It's hardly a terrible burden to have to stick an ng-min step in there as well. It seems like you're trying to justify an instinctive distaste for this feature by exaggerating how problematic it is, when in reality it isn't problematic at all.