LOC means nothing, and if you want to generate subtle programmer errors, then templates is definitely the way to go.
* reading and trying to understand source code
* maintaining source code
* typing and programming-related injuries
The dynamic-typed camp argues that even declaring a variable is a pain. Conciseness is one of the favourite features of JS/Ruby/Python developers and prolixity is universaly loathed in Java.
Please expand on your assertion that subtle programming errors are caused by templates. I'm interested especially in errors as a consequence of using templates from the STL or to build generic code. i.e: not metaprogramming
I think it helps but in general those things are not related very well. For examples guess what this line of code does (this is APL) ?
X[⍋X+.≠' ';]
Please indicate how so. I cannot think of ways that make templates more prone to programmer error than, let's say, str_xxx functions for which the programmer needs to allocate extra room for a \0 (or not, depending on which function you use...). Those types of C idiosyncrasies cause much more mistakes than any inadvertent template overload ever could.