@ianthetechieIan Wagner Thanks for your thoughts! You're right about the catch-and-ignore pattern—it's a common anti-pattern in Java that undermines the benefits of checked exceptions. My blog post actually addresses this and compares Java's approach with Rust's Result<T, E> in detail.

I agree about Kotlin's choice—they sacrificed type safety for convenience. The ideal solution would be improving Java's checked exceptions to work better with modern features like lambdas, rather than abandoning them entirely.