Note the quotes: "ought" to.
Bending the paradigm simply makes things difficult for other programmers maintaining your code, unless it is bent the same way all the time. While I personally dislike checked exceptions - at least when required all of the time; as I mentioned it's handy sometimes to remind me what might get thrown - I've also worked with people that needed such a crutch all of the time. As a result, in mixed shops of varying ability levels, I think that people ought to use checked exceptions. They're expected, and one of the keys to maintenance-friendly programming is "do what's expected".
I've mentioned this [link|/forums/render/content/show?contentid=100013|before], but it bears repeating: Java is a giant compromise that allows mediocre and good programmers to co-exist without killing each other. When I'm programming for/by myself, I don't use Java, for reasons including things like checked exceptions.
