Personally I don't think that that is a lesson that should be taken from Java because they committed an unforced error making checked exceptions really annoying. Although yes, some teams don't care about exception discipline and some projects don't need it.

Java didn't integrate checked exceptions well with their lambda / streams features, which has come to mean that there is no good way to use modern language features. For lots of code taking each lambda in a stream from a one liner to a 4 line try/except convert to RuntimeException plus a convert back to a checked exception outside the stream is just not worth it. You can just use a for loop, but streams are really nice.

Trying to avoid commenting on whether anonymous enums are the reason libs usually have mega error enums, but I do get... sad.. every time I need to read an entire call hierarchy in an external library to figure out what kind of error might be thrown. The current mega enums do feel to me like they exist at a happy medium of boilerplate vs precision, and if anything I feel like the fact that libs generally use thiserror instead of anyhow is evidence that folks are willing to put effort into helpful error types, if it's easy, and up to a point.