Comment Re:Yep... been there, got the 'T' shirt (Score 1) 203
This is funny because this is the standard Erlang philosophy. The question becomes: Are you positive about the state that brought you to the exception and can you recover or should you log and alert and exit from that function? Are you really suggesting to preemptively insert sweeping exception handlers that allow errors in code paths to be ignored and move on? If something is so non-critical then it probably shouldn't be there. OS releases are a frequent cause of version updates anyway. Exception handlers tend to contain the least tested sections of code and I'm seen too many that swallowed errors and hid the problem for long periods of time before being discovered. I'd rather see a crash unless there is an obvious way out with a known state.