Gopher Wrangling. Effective error handling in Go

Re:Gopher Wrangling. Effective error handling in Go by kaba0 on Tuesday June 20, 2023 @03:11AM (#36400675)

Java is absolutely not a complex language. The “enterprise java” style is an unfortunate one that can actually be traced back to C++, but it is not a necessity at all, and due to the sheer size of the java ecosystem you will find plenty of examples of a more barebones approach — also supported by the language developers.

I fail to see why I would go with go over java, besides.. perhaps some CLI app? With Graal even that can be implemented in Java.

[ Parent | on HN ]

Re:Gopher Wrangling. Effective error handling in Go by konart on Tuesday June 20, 2023 @04:01AM (#36400985)

>The “enterprise java” style is an unfortunate one >but it is not a necessity at all

The thing is in real life you have to deal with this kind of code most of the time. Because most of the time you deal with the old code or people who are used to some patterns you have to use too because you are part of the team.

Go enforces (kind of) a more barebones approach by default.

PS: I think it's poinless to compare two languages. We should rather compare real practices and read examples.

[ Parent | on HN ]

Re:Gopher Wrangling. Effective error handling in Go by kaba0 on Tuesday June 20, 2023 @04:45AM (#36401306)

Ad absurdum than a new language will always be better, because usage patterns change and the new language doesn’t yet have any existing code bases using the old ones.

[ Parent | on HN ]