10 Key Takeaways from the 2025 Go Developer Survey

Hello! The Go team at Google recently analyzed responses from 5,379 developers who participated in the 2025 Go Developer Survey. Their feedback paints a vivid picture of where the language stands today and where it needs to go. From AI tool adoption to documentation frustrations, the results highlight three major themes: developers want clearer best practices, better standard library guidance, and modern language features. They also show that while AI coding assistants are widely used, satisfaction is tempered by quality issues. Plus, a surprising number of developers frequently consult help pages for basic go commands, signaling room for improvement. Dive into our top 10 findings from this year's comprehensive survey.

1. Who Responded: A Skilled, Multi-Language Crowd

The survey attracted a highly experienced group: 87% called themselves professional developers, and 82% use Go as their primary work language. Most respondents (75%) have at least six years of professional development experience, but importantly, 81% had more years in other languages before adopting Go. This means Go is rarely a first language. The data reveals a recurring friction point: when Go’s idiomatic patterns differ dramatically from a developer’s more familiar language, it creates a learning curve and ongoing cognitive load. The technology sector made up 46% of responses, but a majority came from diverse industries—finance, healthcare, logistics—proving Go’s reach extends far beyond Silicon Valley.

2. Overall Satisfaction Remains High—But With Caveats

Go continues to earn strong satisfaction ratings overall. Developers praise its simplicity, performance, and concurrency model. However, satisfaction dips when it comes to certain tooling and ecosystem aspects. Many respondents expressed a desire for more guidance on best practices—especially around project structure, error handling, and testing. The survey suggests that while developers love Go’s core philosophy, they sometimes feel lost when applying it to real-world, large-scale projects. There’s a clear appetite for idiomatic examples and official style guides that go beyond the basics. The Go team sees this as an opportunity to invest in documentation, training, and community-led patterns that make best practices more discoverable.

3. Top Challenges: Best Practices and Standard Library Mastery

When asked about their biggest hurdles, developers repeatedly mentioned identifying and applying best practices and making the most of the standard library. Despite Go’s reputation for being straightforward, newcomers—and even some veterans—struggle to know the “Go way” of solving common problems. The standard library is vast and powerful, but its breadth can be overwhelming. Respondents want more curated guides, cookbook-style examples, and maybe built-in linters that suggest idiomatic replacements when they spot non-standard patterns. Addressing these challenges would reduce cognitive friction and help developers write more consistent, maintainable code.

4. AI-Powered Tools Are Everywhere—But Quality Worries Persist

A striking 78% of respondents said they use AI tools (e.g., GitHub Copilot, ChatGPT, or other code assistants) for Go development. Common use cases include learning how to use a module, writing repetitive boilerplate, and debugging. However, satisfaction scores were only middling—around 3.5 out of 5. The primary reason: quality concerns. Developers reported that AI-generated Go code often misses idiomatic practices, introduces subtle bugs, or fails to leverage the standard library effectively. The Go team sees this as a call to improve the training data and tool integrations so that AI assistants better reflect actual Go conventions.

5. The go Command Help System Needs an Overhaul

One of the survey’s more surprising findings: a high proportion of developers frequently consult documentation for core go subcommands like go build, go run, and go mod. This suggests that the built-in help system isn’t as intuitive or discoverable as it could be. Many respondents wished for clearer explanations, examples right in the terminal, and perhaps a new interactive help mode. Improving the go command’s help output could reduce context-switching to web browsers and increase developer flow. The Go team is now exploring ways to revamp the help experience—maybe even with hyperlinked text or inline examples.

6. What Developers Are Building With Go

Go remains the language of choice for cloud-native infrastructure, APIs, and microservices. The survey confirmed that 68% of respondents build web backends, 52% work on CLI tools, and 38% develop DevOps scripts. There’s also growing interest in data processing pipelines, with 22% using Go for that purpose. Interestingly, a small but dedicated group (7%) is using Go for game development or embedded systems. These usage patterns reinforce Go’s sweet spot: high-performance, networked services. But they also highlight areas where the standard library’s HTTP and networking packages are cherished, while also showing demand for more first-party support in areas like database drivers and serialization.

7. Development Environments: Editors, Operating Systems, and More

The survey delved into developers’ workspaces. Visual Studio Code dominated editor choice (64%), followed by GoLand (23%) and Vim/Neovim (12%). On the OS front, macOS led (56%), then Linux (34%), and Windows (10%). Notably, 55% of respondents work in containers at least sometimes, and 41% use Go in a CI/CD environment daily. These numbers underscore the need for Go tooling that integrates well with VS Code and container workflows. Respondents also asked for better gopls (the Go language server) performance and more reliable refactoring support.

8. The Multi-Language Developer Experience

Since most Go developers also use other languages (Python is the most common second language, followed by JavaScript and Rust), the survey explored cross-language friction. Respondents frequently reported that switching between language idioms is mentally taxing. For example, Python developers might initially struggle with Go’s error handling approach, while Rust developers may miss pattern matching. There’s a clear demand for language-specific onboarding tips and tools that can auto-detect a developer’s background and offer relevant guidance. The Go team is considering creating “transition guides” for popular source languages.

9. Community and Open Source Engagement

An encouraging 72% of respondents use Go for personal or open-source projects, showing the community’s health and vitality. However, contributions to the Go project itself are much lower (about 5%). Feedback on community resources like the official blog, forums, and Go Wiki was generally positive, but many wish for more curated learning paths and a centralized hub for tutorials. The survey also highlighted a desire for more inclusive, beginner-friendly events. The Go team is working to amplify community-led initiatives and improve discoverability of high-quality third-party resources.

10. Future Directions: Language and Tooling Improvements

Finally, developers were asked what they’d most like to see in future Go releases. The wish list includes: generics improvements (more flexible type parameters), better error handling syntax, pattern matching, and enhanced support for result types. On the tooling side, they want built-in support for hot reloading, a more powerful go test with coverage details, and first-class profiling within the standard command set. The Go team is already experimenting with some of these ideas—for example, a proposed try keyword for streamlined error handling. The survey gives them a data-driven roadmap to prioritize what matters most to the community.

These 10 takeaways only scratch the surface of the 2025 Go Developer Survey. The complete data set provides even deeper insights into how developers work, what frustrates them, and what excites them about Go’s future. If you’d like to explore the raw numbers, the full report is available on the Go Blog. In the meantime, the Go team is already acting on your feedback—so look forward to improvements in documentation, AI integrations, and the go command experience. Thank you to everyone who responded; your voice shapes the language we all love.