I'm really, really sorry that most of today's developers (it seems) consider checked exceptions to be a bad practice. Sometimes I feel like I'm the only person

I'm really, really sorry that most of today's developers (it seems) consider checked exceptions to be a bad practice. Sometimes I feel like I'm the only person in the world still advocating their usage. I'm currently working on an application that uses libraries developed by people who had the same opinion about checked exceptions as you. Of course, their code still throws exceptions. Except now, I don't know whether a method I call can throw an exception and whether I should write code to handle it until it all blows up at runtime (more often than not - in production). So what do I do then? I write a try-catch to handle their exception. The exact same thing I would have done had they decided to throw a checked exception. Only now, I don't get any warning that I should handle possible exceptional behavior at compile time, I get it at some point during runtime.