Eval considered

Using eval is almost always a bad idea. It's a crutch for bad designs, it opens giant security holes in your code, and in practice it's almost never needed to get actual stuff done.

>>7
Mental overhead is unavoidably greater than O(project size) regardless of the language paradigm, so the only way I can see you having more more overhead with FP is if you don't structure your programs correctly.
Thus, the fabricated quote was a sardonic commentary on how I assume >>5 structures their projects.

w4c /prog/ wouldn't have needed that explaining.