I think you're confusing input validation with error messages here. A script should produce meaningless fluff for errors a visitor cannot fix anyway - like could not open /path/to/config/file
. That stuff belongs in the server error log and nowhere else. Of course it is useful to tell the user what went wrong if his input
was rejected for some reason, but that's not quite the same as an error message. As Ovid
wrote in his tutorial, your script may break at any - even unforseen - point, so you have no control about what information a visitor may see if you indiscriminately set fatalsToBrowser
Makeshifts last the longest.