Exceptions should not be handled – they should be aggregated

User entering wrong input is a logical condition and typically handling a logical condition (point being it's not an error from the software's operational point of view) using tools that allow easier logic flow (i.e. error codes) etc.

Out of memory error can happen in many environments because for example in C++ it's about the allocator. You might have a custom allocator with some limit that has no bearing whatsoever what the OS does.

  * Use asserts/panics for bugs.
  * Use "error codes/values/enums" for logical conditions (that are errors to the user, not errors to the software)
  * Use exceptions for unexpected errors in the execution of the software (normally more or less just resource allocation failures)

Working under a simple structure to expect the best of people I am mandated to presume you read the article leaving me confused as to how your comment relates to social sciences. This causes me great discomfort and although objectively irrational, leads me to wish that the authors soon conclude their future work on exception aggregation to resolve the situation. This also reinforces my past evaluation that the Japanese sure are an interesting bunch.