Go Developer Survey 2022 Q2 Results

Post by treis » Thu, Sep 08, 2022, 6:09 PM UTC

klodolph wrote: post #17

aniforprez wrote: post #5

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…

I would love to see some in-depth discussion about this. Even in 2022, I don't think it's clear what we want error handling to look like. You can ask for correctness guarantees from the compiler, but it's easy to ask, it's harder to design a system that actually works. > 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…

Post by Thaxll » Thu, Sep 08, 2022, 6:13 PM UTC

bragr wrote: post #10

verdverm wrote: post #4

Earlier quoted context omitted.

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 by biztos » Thu, Sep 08, 2022, 6:14 PM UTC

just-ok wrote: post #70

bheadmaster wrote: post #46

Earlier quoted context omitted.

I find go's package system very convenient for quick projects: go mod init [write code] go mod tidy go build It's definitely more convenient than Python's venv dance.

Python’s venv dance only really comes into play if you need a third-party dependency that you haven’t installed globally. The Go dance is always necessary, which makes it slightly more annoying for short scripts or tests. I usually resort to the Go playground for them.

     echo 'package main
 import "fmt"
 func main() { fmt.Println("hello"); }
 ' > foo.go && go run foo.go

Post by randomdata » Thu, Sep 08, 2022, 6:16 PM UTC

hajile wrote: post #45

Almost 40% of respondents either use generics or want to use generics. That's a pretty quick uptake given the decade of loud, prominent voices shouting that go didn't need and shouldn't have generics.

Post by cityzen » Thu, Sep 08, 2022, 6:20 PM UTC

silisili wrote: post #35

awb wrote: post #8

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.

I recently spent about 3 weeks looking for new Go positions, just by advertising open for work on LinkedIn. There are plenty of companies interested, many of them startups. I don't think anyone with a strong Go background looking for a job right now would have any trouble at all.