Goodbye, Clean Code

Re:Goodbye, Clean Code by loopz on Sunday January 12, 2020 @12:40PM (#22027640)

Is it really: Are programmers omniscient then that they can trap all kinds of exceptions correctly from external code? It's a sophisticated method that dumps the problem on the user instead.

Golang also output stack traces and even supports panic() if one wants to have something similar to handling exceptions. The difference is that this is used for classes of errors that ideally are programmer error, and not for all kinds of business logic states. I'm not saying the Go Way is perfect either, but it's at least a small step acknowledging the difference, rather than defaulting to dumping random programmer errors on unsuspecting users.

Errorhandling is easier when improving design. The problem is this takes time, thinking and effort.

[ Parent | on HN ]

Re:Goodbye, Clean Code by hota_mazi on Sunday January 12, 2020 @02:26PM (#22028552)

Go didn't discover anything. Java's runtime and checked exceptions are already the direct consequence of errors being of two kinds: recoverable and non recoverable.

Go's approach is inferior to Java's in all ways.

[ Parent | on HN ]

Re:Goodbye, Clean Code by int_19h on Monday January 13, 2020 @02:40AM (#22032595)

Exceptions are basically error types with dynamic typing in an otherwise statically typed language. So if you can deal with dynamic typing in Python, you can handle exceptions in Java.

[ Parent | on HN ]