Why even teach it/include it at all? I fear that other developers will read a comment like this three months down the road and take it hook, line, and sinker.

Why even teach it/include it at all? I fear that other developers will read a comment like this three months down the road and take it hook, line, and sinker. It is in line with the narrative that AngularJS and similar tools hide their complexity/inflexibility, and that the up-front examples are marketing fluff. I know I am guilty of this when I look to comments like this one for the "on the ground" perspective. Real-world AngularJS applications use multiple templates and {{ o.p }}. {{ o.p }} is the recommended way to render scope 99% of the time. ngmin[1] solves the DI minification/annotation problem transparently and is trivial to integrate into any existing build process. [1] https://github.com/btford/ngmin https://github.com/btford/ngmin