4 ms·
an exception is better than a silent failure in almost all situations. this is an argument for not using 200 for all; not against
by rickycook 11y ago
an exception is better than a silent failure in almost all situations.
this is an argument for not using 200 for all; not against
- mootothemax 11y ago>an exception is better than a silent failure in almost all situations. >this is an argument for not using 200 for all; not against The practical side of me disagrees. Experience bears out that plenty of developers are at a loss when e.g. a login callback page shows an unhandled exception error despite error-checking code being in place and running against the response's "error" node or whatever is used. The problem is that there just aren't enough people out there that can understand the entire stack, and the end result is that people who've paid (good/bad) money for development - and their end users - end up with services that'd otherwise be decently functional showing the odd exception error instead. (the technical side of me agrees with you absolutely!)