Now, Gosling has responded, and here is the page with comments on the article.
My current thinking is that we programmers want to get things to work and worry about the errors later. That's when we run into problems. At work people talk about getting the sunny day scenarios done and leaving the hard parts for last. I think that's leaving a critical requirement out. It's like trying to shoehorn in a security model at the last minute.
Gosling is not telling the whole truth when he talks about wrapping Exceptions. I think that's the right thing to do, but prior to 1.4 it required rolling your own Exception class if you wanted to pass along the original stack trace.
