undefined | Better HN

0 pointsbsder2y ago0 comments

One of these things is not like the others ...

The first 3 need to terminate your thread because something is irretrievably incorrect. The only sane thing to do is stop.

"UnsupportedEncodingException" has lots of things you can do to recover. You can try different encodings. You can request retry of someting. You can check a CRC for corruption. etc.

So, the first 3 really shouldn't litter your code. The final one probably should.

0 comments

3 comments · 1 top-level

invalidname2y ago· 2 in thread

Finally a person who knows Java ;-)

For other readers the first 3 are all runtime exceptions and the last one is a checked exception that a lot of people complain about...

I think the last one is an example of why people hate checked exceptions and the solution to this was to create newer APIs that focus on UTF-8 that just don't throw that exception.

bsderOP2y ago

Why is "UnsupportedEncodingException" an issue?

It should throw only on creation and then never be an issue from that point forward, no?

If it's throwing everywhere then, as you point out, that is an API problem rather than a problem with exceptions, themselves.

invalidname2y ago

Yes. It's 100% an API problem...

j / k navigate · click thread line to collapse