Yeah, nothing is better than a whole lot of corrupt business data! It's so much better to have the system not crash than collect incorrect money amounts or send 10 million unpaid widgets out.
When an exception occurs and the system goes down, you get a nice notification and a stack trace. From there you can actually go about fixing the problems created by those hordes of crappy Java programmers rather than just ignoring the problem and hope that nobody will notice.
"The trouble is that every time you call a method that throws an exception, you create an immediate crisis: you break the build. Rather than conciously planning an error handling strategy, programmers do something, anything, to make the compiler shut up."
Now, granting that people like that are even paid to write code, do you think they're allowed to work on systems that ship widgets or cause money to change hands?
Frankly, we're having an absurd discussion because the assumption introduced by the original article is absurd. Nobody programs that way, or rather the few people who program that way can't be made productive through any means short of torture.
When an exception occurs and the system goes down, you get a nice notification and a stack trace. From there you can actually go about fixing the problems created by those hordes of crappy Java programmers rather than just ignoring the problem and hope that nobody will notice.