> Lots of us have since observed that this approach to failure leads to errors because programmers ignore failures, allowing them to be handled by a catch-all at the top of the stack, which typically just dumps a stacktrace and calls it a day.
That's not typical Java code. You could do that in quick & dirty code, but I haven't seen such code in production code.
That's not typical Java code. You could do that in quick & dirty code, but I haven't seen such code in production code.