Use strict does have an overhead

?? Well, that is pretty darn misleading. use strict has a very, very tiny overhead such that most people that I respect and who I've heard weigh in on the subject feel that the work of adding and removing strict between testing and production (and more importantly, the risk of forgetting to add it back in each time changes are made) outweigh the cost by a wide margin.

Taint checking is also something that should not be disabled in production (even more so than strict).

Warnings, however, are much easier to justify removing from production. Perhaps the best situation would be to keep warnings enabled but have a separate infrastructure for collecting warnings information and making sure the volume of information can't become a burden.

But if you don't create a separate infrastructure for warnings, I'd definitely turn them off in production.

        - tye (but my friends call me "Tye")