faun.dev
Go Developer Survey Is Out
The 2025 Go Developer Survey reveals developers' desire for better best practices, enhanced standard library usage, and modernized tooling. AI-powered development tools are common, yet satisfaction is moderate due to quality concerns. Most respondents are experienced developers in the tech industry, highlighting challenges like ensuring code quality and finding reliable modules. ### Key Points ... A major challenge for Go developers is identifying and consistently applying idiomatic best practices, along with finding trustworthy third-party modules. Use of AI-powered development tools is now common among Go developers, but overall satisfaction remains moderate due to concerns about code quality and reliability. … ... The **2025 Go Developer Survey** is out and it offers a clear snapshot of where the Go ecosystem stands today and where friction remains. Developers broadly value Go as a stable, productive platform, but they are asking for more guidance on **best practices**, better ways to **leverage the standard library**, and **modernized tooling** to reduce day-to-day friction. AI-powered development tools are now widely used among Go developers, particularly for learning, boilerplate generation, unit tests, and autocompletion. However, satisfaction remains moderate. The dominant concern is **code quality**: AI-generated output often requires careful review, corrections, and contextual adjustments, which limits trust and caps productivity gains. AI is seen as helpful for reducing toil, not as a reliable autonomous coder. The survey highlights a recurring usability issue with Go's tooling: **core command documentation**. A significant number of developers report frequently revisiting documentation for fundamental commands such as `go build`, `go run`, and `go mod`. The current help system is functional but not discoverable or ergonomic enough - this is what the data suggests. … Three challenges dominate developer feedback: - Difficulty identifying and enforcing best practices. - Missing language features commonly found elsewhere, particularly around **error handling**, **enums**, and expressiveness. - Trouble identifying **trustworthy third-party modules**, with developers asking for stronger quality signals, maintenance indicators, and usage context. … 28 % Percentage of respondents frustrated by missing language features found in other languages. 26 % Percentage of respondents reporting difficulty finding trustworthy Go modules. 53 % Percentage of respondents using AI-powered development tools daily. 29 % ... 55 %
Related Pain Points5件
Go lacks modern language features like generics, enums, and pattern matching
728% of developers want language features missing from Go that are available in other languages. Common requests include proper enums, union types, sum types, pattern matching, and nil pointer safety. Existing generics are criticized as half-baked.
Difficulty identifying and applying idiomatic Go patterns
633% of Go developers struggle to ensure their code follows idiomatic patterns and best practices. Developers switching between Go and other languages face cognitive load, and many request official guidance and tooling support to enforce idioms.
Difficulty identifying trustworthy and reliable third-party modules
526% of developers report difficulty finding trustworthy Go modules. Developers lack reliable quality signals, maintenance indicators, and usage context to evaluate third-party modules.
AI-powered development tools produce low-quality code
5While most Go developers use AI tools for learning and coding tasks, satisfaction is middling. 53% report that tools create non-functional code, and 30% complain that even working code is poor quality. AI struggles with complex features.
Go CLI tools have poor documentation and help navigation
315-25% of developers frequently need to review documentation for common Go CLI subcommands like `build` and `run`. The underlying issue is navigating and parsing the help system itself rather than just remembering flags.