4 ms·
> // dunno panic This is exactly why Java is such a pain to work with. Somehow, Java developers all decided to stop dealing with error conditions and just cra
by jeroenhd 5mo ago
> // dunno panic
This is exactly why Java is such a pain to work with.
Somehow, Java developers all decided to stop dealing with error conditions and just crash the stack whenever something weird happens.
The way Java developers seem to work these days has a lot in common with Rust beginners that just `?` or `.unwrap()` every single fallible method. Random crashes ("RuntimeException") are acceptable, so nobody even bothers doing error handling any more.
Even the base SDK doesn't really bother with handling exceptions (i.e. the story with streams + exceptions). It's an excellent language feature tainted by a combination of bad choices twenty years ago and a weird culture shift in error handling.
- vips7L 5mo agoThere’s plenty of errors that aren’t able to be handled. But yes I agree most developers don’t understand exceptions. They seem to be scared of them tbh and there’s lots of bad advice floating around about them. Like “exceptions should be exceptional” or “don’t use exceptions for control flow”. I am beginning to see a culture shift as the old guard dies out though.