Why Go Will NEVER Fix Error Handling

I was a part of the ? discussion and it just blows my mind how they came up with a good concept and still backed down... We might get arrow functions in Go before a better error handling approach.

Great example of "Perfect is the enemy of good".

that's the golang version of 'you think you do but you don't'

When porting from PHP to Go, explicit error handling helped us find some data consistency bugs because we actually started thinking about error handling. And we found that some lines could throw and break our code (which would result in data corruption) because we didn't realize it could throw and we had no handling in place

i respect that they do not include every single crap into language like many other langunges do (i am looking at you, c++), they meticulously try and look the outcome, does it worth bloating a language with specific feature or not! This is one of the reason, why i like Go!

working 7 years with java, 1 year with kotlin, 1 year with scala; and now 4 months with go, i dont mind the current error handling at all. Direct and explicit, easy to track when debugging, everything that we devs need

where I spend my time the most is thinking what message should I put in the error

The single questionmark as an alias of if err != nil { return err } would be a nice addition. I'm not too sure about the curly brackets after where you can write what happens if the err is not nil.

22:16 this is a variation of the dangerous “But Sometimes!” argument where an idea that might otherwise be vastly superior in a multitude of ways is dismissed because of some tiny new unforeseen issue. Technology Connections has a fantastic video on the subject, and I personally believe it should be required viewing for anyone going into any kind to engineering field

I like that when someone asks Prime a coding question he answers in ernest