Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Go Developer Survey 2022 Q2 Results

go.dev

Post reply on HN
Print view View original

1–10 of 186 posts

Re: Go Developer Survey 2022 Q2 Results

#2

Post by tapanjk »

TLDR (listed under "key findings" in the post):

- Generics has seen quick adoption.

- Fuzzing is new to most Go developers.

- Third-party dependencies are a top security concern.

- We can do better when announcing new functionality.

- Error handling remains a challenge.

Re: Go Developer Survey 2022 Q2 Results

#5

Post by aniforprez »

I'm genuinely hoping that after generics, the focus will be on error handling from the survey results

Go devs in a lot of communities love to put their heads in the sand going "error handling is perfectly fine". But it's not fine. Not even close. And I'm very happy there's a lot of demand for some solution in this space. It's just plain too verbose without any of the actual benefits of that verbosity. You don'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't care if you'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'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'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't make the language perfect but it would probably make for the most pleasant development experience for building APIs and services

Re: Go Developer Survey 2022 Q2 Results

#6

Post by ptsneves »

tapanjk wrote: post #2

TLDR (listed under "key findings" in the post): - Generics has seen quick adoption. - Fuzzing is new to most Go developers. - Third-party dependencies are a top security concern. - We can do better when announcing new functionality. - Error handling remains a challenge.

Error handling remains a challenge, but as satisfaction is high it gets no answer at all. Not a single paragraph, how unfortunate. It hits at my major quip with Go: that I do not trust it's governance structure.

Otherwise I really like using it, and would replace it everywhere python is used.

Re: Go Developer Survey 2022 Q2 Results

#8

Post by awb »

As a developer, Go seemed so promising 5-10 years ago. But as a recruiter, I never saw any kind of stable movement towards Go adoption among startups.

Hard to tell why that was because functionally and programmatically it’s a really clean, efficient language and tooling stack.

Re: Go Developer Survey 2022 Q2 Results

#9

Post by melony »

My main gripe with Go is that a large percentage of first-party documentation is not kept up to date well. If you dive deeply into Go's concurrency patterns, many of the recommended readings are old blogposts from 2014-2016. When the behaviour of the internals change, these blogposts are not clearly marked as deprecated either.

For example this post

https://go.dev/blog/pipelines

should clearly mention that it can still be considered current up to the latest version of Go. First-party documentation needs to be held to higher standards.

Re: Go Developer Survey 2022 Q2 Results

#10

Post by bragr »

verdverm wrote: post #4
mfer wrote: post #3

I wish they would ask what makes it difficult to work with dependencies in Go.

What is difficult? I find them very refreshing compared to other dep mgmt systems. They also have a lot of secondary benefits most are not aware of. https://verdverm.com/go-mods

I find go's package system both too cumbersome for small/quick projects, and yet leaving me wanting in more complex scenarios. It's gotten better of the years, but I never really enjoy my encounters with go-mods
Post reply on HN