Checked exceptions are also in ADA.
(Warning, this post contains strongly held beliefs that you might find confronting.)
Programmers don't like them and complain, or write exception swallowing code.
Checked exceptions exist because things can not only fail to work, you can do a failure mode/effects analysis and determine this in advance.
File reads can fail. RPC calls can fail. Network IO can fail. Data can be mis-formatted when parsed.
The "happy path" for code is easy.
I knew a guy at University who could write great "happy path" code. None of the edge cases ever worked. These days he does Python for an open source company. Nuff said.
If you don't want to handle checked exceptions, what you're really saying is
While I'm writing this code, I don't want to consider obvious failure modes.
The User will just have to like the program crashing or doing weird things.
But that's okay with me because
I'm so much more important than the people who will have to use the software
in the real, messy, error-prone world.
After all, I write the code once, you use it all day long.
So checked exceptions are not going to be liked by programmers, because it means more work.
Of course, other people might have wanted that work done.
They might have wanted the right answer even if the file server failed/ USB stick dies.
It's a strange belief in the programming community that you should be using a programming language that makes your life easier, that you enjoy, when your job is to write software. You job is solving someones problem, not letting you engage in programmatic Jazz improvisation.
If you're an amateur programmer (not programming for money), feel free to program in C# or some other language with no checked exceptions. Heck, cut out the middle man and program in Logo. You can draw pretty patterns on the floor with the turtle.