codeinabox@programming.dev to Golang@programming.devEnglish · 12 days agoResults from the 2025 Go Developer Surveygo.devexternal-linkmessage-square7linkfedilinkarrow-up115arrow-down10file-textcross-posted to: lobsters@lemmy.bestiver.se
arrow-up115arrow-down1external-linkResults from the 2025 Go Developer Surveygo.devcodeinabox@programming.dev to Golang@programming.devEnglish · 12 days agomessage-square7linkfedilinkfile-textcross-posted to: lobsters@lemmy.bestiver.se
minus-squarekamstrup@programming.devlinkfedilinkarrow-up1·1 day agoI am perplexed that they refuse to acknowledge some pretty deep issues I see every major Go project run into: There are corner cases where it is literally impossible to check of the value of a type-param interface is nil. Type-params on methods Type-safe enums
I am perplexed that they refuse to acknowledge some pretty deep issues I see every major Go project run into: