News for hackers. Stuff that matters.
Re:Program your next server in Go by vertex-four on Tuesday June 07, 2016 @05:28PM (#11858033)
So as someone who's written some Go, I'd argue that Go is the screwdriver - it's one of the only modern languages which explicitly refuses to tackle the error handling problem, which has resulted in some of my code being more about the failure case than the success case.

Of course, others will disagree - fine. But to argue that e.g. Java is definitely the screwdriver is a subjective judgement.

Re:Program your next server in Go by eropple on Tuesday June 07, 2016 @05:46PM (#11858193)
To add to this: Go's inexpressivity (hi, generics!) makes common patterns that I see in Kotlin, Java, and Scala (as well as Rust, off-JVM) makes error handling a complete bear, to the point where my eyebrows are really raised at vertex-four being downvoted for this.

The use of please-check-this error conditions instead of something like a Try<T, E> (Result<V, E> in Rust) and an inability to just map over these as 0- or 1-element collections is such a huge pain, and it certainly does matter when you're piling up multiple error-handling cases. Even more when you'd otherwise use Scala's `recover` to get back on a happy path. Go's inexpressivity directly impinges on one's ability to get things done.

(Food for thought: forgetting to handle the error case from Rust's Result<V, E> is a compiler error. Is "if err != nil" really that good an idea in such a universe?)

Re:Program your next server in Go by chrismorgan on Tuesday June 07, 2016 @07:49PM (#11858989)
Not using a Result is a warning, not an error: https://is.gd/U43rdG
Re:Program your next server in Go by eropple on Tuesday June 07, 2016 @08:00PM (#11859037)
Sorry, yes (I compile with warnings as errors), good catch.
Re:Program your next server in Go by mratzloff on Wednesday June 08, 2016 @01:45AM (#11860272)
You must explicitly ignore errors in Go.

result, _ := someFunc()

Re:Program your next server in Go by kasey_junk on Wednesday June 08, 2016 @07:14AM (#11861425)
Not if they are the only return value. You should use an analysis tool to avoid this but nothing about the language requires it.
Re:Program your next server in Go by mratzloff on Thursday June 09, 2016 @10:40AM (#11869650)
Ah, you are right.