Go Developer Survey 2022 Q2 Results
I&#x27;m genuinely hoping that after generics, the focus will be on error handling from the survey results<p>Go devs in a lot of communities love to put their heads in the sand going &quot;error handling is perfectly fine&quot;. But it&#x27;s not fine. Not even close. And I&#x27;m very happy there&#x27;s a lot of demand for some solution in this space. It&#x27;s just plain too verbose without any of the actual benefits of that verbosity. You don&#x27;t have compile time checks for errors. Ignoring errors continues to be incredibly easy. The lack of exhaustive switch case statements makes this worse because the compiler doesn&#x27;t care if you&#x27;re handling all the expected error types (or unexpected ones). If you simply want to push errors up the chain to be handled elsewhere you&#x27;re adding 3 lines of code in every function that just does `if err != nil { return nil, err }`. This much verbosity means almost every developer&#x27;s eyes just glaze over all this code during review which I find to be quite dangerous. If this one thing is adequately fixed in Go, it wouldn&#x27;t make the language perfect but it would probably make for the most pleasant development experience for building APIs and services