blog: add 2025 developer survey results
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that tt's the gestalt, rather than any one thing. These folks are telling us there's tremendous value is Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developer value the domains it does well support via stdlib and built-in tooling.Typo:
```suggestion
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that it's the gestalt, rather than any one thing. These folks are telling us there's tremendous value is Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developer value the domains it does well support via stdlib and built-in tooling.
```
The third major frustration was finding trustworthy Go modules. Respondents often described two aspects to this problem. One is that they considered many 3rd-party modules to be of marginal quality, making it hard for really good modules to stand out. The second is identifying which modules are commonly used and under which types of conditions (including recent trends over time). These are both problems that could be addressed by showing what we'll vaguelly call "quality signals" on pkg.go.dev. Respondents provided helpful explanations of the signals they use to identify trustworthy modules, including project activity, code quality, recent adoption trends, or the specific organizations that support or rely upon the module.Typo:
```suggestion
The third major frustration was finding trustworthy Go modules. Respondents often described two aspects to this problem. One is that they considered many 3rd-party modules to be of marginal quality, making it hard for really good modules to stand out. The second is identifying which modules are commonly used and under which types of conditions (including recent trends over time). These are both problems that could be addressed by showing what we'll vaguely call "quality signals" on pkg.go.dev. Respondents provided helpful explanations of the signals they use to identify trustworthy modules, including project activity, code quality, recent adoption trends, or the specific organizations that support or rely upon the module.
```
> "Many pacakges are just clones/forks or one-off pojects with no history/maintenance."Do we need to fix typos here?
```suggestion
> "Many packages are just clones/forks or one-off projects with no history/maintenance."
```
This survey was conducted between Sept 9 - Sept 30, 2025. Participants were publicly invited to respond via the Go Blog, invitations on social media channels (including Bluesky, Mastodon, Reddit, and X), as well as randomized in-product invitations to people using VS Code and GoLand to write Go software. We received a total of 7,070 responses. After data cleaning to remove bots and other very low quality responses, 5,379 were used for the remained of our analysis. The median survey response time was between 12 – 13 minutes.Typo:
```suggestion
This survey was conducted between Sept 9 - Sept 30, 2025. Participants were publicly invited to respond via the Go Blog, invitations on social media channels (including Bluesky, Mastodon, Reddit, and X), as well as randomized in-product invitations to people using VS Code and GoLand to write Go software. We received a total of 7,070 responses. After data cleaning to remove bots and other very low quality responses, 5,379 were used for the remainder of our analysis. The median survey response time was between 12 – 13 minutes.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Found a few assorted typos while skimming.
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that tt's the gestalt, rather than any one thing. These folks are telling us there's tremendous value is Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developer value the domains it does well support via stdlib and built-in tooling.```suggestion
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that tt's the gestalt, rather than any one thing. These folks are telling us there's tremendous value in Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developers value the domains it does support well via stdlib and built-in tooling.
```
Minor typo fixes ("developers" and "in go" vs "is go").
Also "well support" is much less standard than the reversed form
This year we asked the Go community to share your sentiment towards the Go project itself. These results were quite different from the 91% satisfaction rate we discussed above, and point to areas the Go Team plans to invest in during 2026. In particular, we want to encourage more contributors to get involved, and ensure the Go Team accurately understands the challenges Go developers currently face. We hope this focus, in turn, will help to increase developer trust in both the Go project and the Go Team leadership. As one respondent explained the problem:```suggestion
This year we asked the Go community to share their sentiment towards the Go project itself. These results were quite different from the 91% satisfaction rate we discussed above, and point to areas the Go Team plans to invest in during 2026. In particular, we want to encourage more contributors to get involved, and ensure the Go Team accurately understands the challenges Go developers currently face. We hope this focus, in turn, will help to increase developer trust in both the Go project and the Go Team leadership. As one respondent explained the problem:
```
This year we asked the Go community to share your sentiment towards the Go project itself. These results were quite different from the 91% satisfaction rate we discussed above, and point to areas the Go Team plans to invest in during 2026. In particular, we want to encourage more contributors to get involved, and ensure the Go Team accurately understands the challenges Go developers currently face. We hope this focus, in turn, will help to increase developer trust in both the Go project and the Go Team leadership. As one respondent explained the problem:On another note, this mentions "go team" 5 times in 4 sentences, which (IMO) borders on repetitive.
We should ideally find another synonym to avoid sounding like a broken record.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thanks for the feedback and suggestions! I've incorporated these into the latest draft.
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that tt's the gestalt, rather than any one thing. These folks are telling us there's tremendous value is Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developer value the domains it does well support via stdlib and built-in tooling.```suggestion
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that tt's the gestalt, rather than any one thing. These folks are telling us there's tremendous value in Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developers value the domains it does support well via stdlib and built-in tooling.
```Minor typo fixes ("developers" and "in go" vs "is go").
Also "well support" is much less standard than the reversed form
Done
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that tt's the gestalt, rather than any one thing. These folks are telling us there's tremendous value is Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developer value the domains it does well support via stdlib and built-in tooling.Todd KuleszaTypo:
```suggestion
Why are respondents so positive about Go? Looking at open-text responses to several different survey questions suggests that it's the gestalt, rather than any one thing. These folks are telling us there's tremendous value is Go as a holistic platform. That doesn't mean it supports all programming domains equally well (it surely does not), but that developer value the domains it does well support via stdlib and built-in tooling.
```
Done
This year we asked the Go community to share your sentiment towards the Go project itself. These results were quite different from the 91% satisfaction rate we discussed above, and point to areas the Go Team plans to invest in during 2026. In particular, we want to encourage more contributors to get involved, and ensure the Go Team accurately understands the challenges Go developers currently face. We hope this focus, in turn, will help to increase developer trust in both the Go project and the Go Team leadership. As one respondent explained the problem:On another note, this mentions "go team" 5 times in 4 sentences, which (IMO) borders on repetitive.
We should ideally find another synonym to avoid sounding like a broken record.
Acknowledged
The third major frustration was finding trustworthy Go modules. Respondents often described two aspects to this problem. One is that they considered many 3rd-party modules to be of marginal quality, making it hard for really good modules to stand out. The second is identifying which modules are commonly used and under which types of conditions (including recent trends over time). These are both problems that could be addressed by showing what we'll vaguelly call "quality signals" on pkg.go.dev. Respondents provided helpful explanations of the signals they use to identify trustworthy modules, including project activity, code quality, recent adoption trends, or the specific organizations that support or rely upon the module.Typo:
```suggestion
The third major frustration was finding trustworthy Go modules. Respondents often described two aspects to this problem. One is that they considered many 3rd-party modules to be of marginal quality, making it hard for really good modules to stand out. The second is identifying which modules are commonly used and under which types of conditions (including recent trends over time). These are both problems that could be addressed by showing what we'll vaguely call "quality signals" on pkg.go.dev. Respondents provided helpful explanations of the signals they use to identify trustworthy modules, including project activity, code quality, recent adoption trends, or the specific organizations that support or rely upon the module.
```
Done
> "Many pacakges are just clones/forks or one-off pojects with no history/maintenance."Do we need to fix typos here?
```suggestion
> "Many packages are just clones/forks or one-off projects with no history/maintenance."
```
Thanks for reviewing this and catching these typos! With participant quotes, we generally leave the original text as-is and add [sic] to indicate that this wasn't an editing or transcription error.
This survey was conducted between Sept 9 - Sept 30, 2025. Participants were publicly invited to respond via the Go Blog, invitations on social media channels (including Bluesky, Mastodon, Reddit, and X), as well as randomized in-product invitations to people using VS Code and GoLand to write Go software. We received a total of 7,070 responses. After data cleaning to remove bots and other very low quality responses, 5,379 were used for the remained of our analysis. The median survey response time was between 12 – 13 minutes.Typo:
```suggestion
This survey was conducted between Sept 9 - Sept 30, 2025. Participants were publicly invited to respond via the Go Blog, invitations on social media channels (including Bluesky, Mastodon, Reddit, and X), as well as randomized in-product invitations to people using VS Code and GoLand to write Go software. We received a total of 7,070 responses. After data cleaning to remove bots and other very low quality responses, 5,379 were used for the remainder of our analysis. The median survey response time was between 12 – 13 minutes.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This year we asked the Go community to share your sentiment towards the Go project itself. These results were quite different from the 91% satisfaction rate we discussed above, and point to areas the Go Team plans to invest in during 2026. In particular, we want to encourage more contributors to get involved, and ensure the Go Team accurately understands the challenges Go developers currently face. We hope this focus, in turn, will help to increase developer trust in both the Go project and the Go Team leadership. As one respondent explained the problem:Todd Kulesza```suggestion
This year we asked the Go community to share their sentiment towards the Go project itself. These results were quite different from the 91% satisfaction rate we discussed above, and point to areas the Go Team plans to invest in during 2026. In particular, we want to encourage more contributors to get involved, and ensure the Go Team accurately understands the challenges Go developers currently face. We hope this focus, in turn, will help to increase developer trust in both the Go project and the Go Team leadership. As one respondent explained the problem:
```
Acknowledged
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hi folks, the public blog post with our survey results is ready for your review. In particular, I want to ensure we're all comfortable with the content and interpretations shared here; if there's anything you'd like me to adjust, let me know. I'll be doing another proof-read of it this weekend and will also fix some hard-to-read chart colors, with a goal of publishing this on Wednesday.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Really great work! My suggestions are very superficial; the substance was extremely well written and super interesting.
domains equally well (it surely does not), but that developers' value the```suggestion
domains equally well (it surely does not), but that developers value the
```
> "The entire reason I use Go is the great tooling and standard library. I'm```suggestion
> "The entire reason I use Go is the great tooling and standard library. I'm
```
codebases or projects. One way to alleviate this additional load is clear,Perhaps this should be a colon?
Unfortunately embedded use cases were left off of the revised list, but we'll```suggestion
Unfortunately, embedded use cases were left off the revised list, but we'll
```
the early hypeShould there be a period at the end of this sentence?
than other toilsome tasks, though we don't yet have strong understanding of```suggestion
than other toilsome tasks, though we don't yet have a strong understanding of
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
domains equally well (it surely does not), but that developers' value the```suggestion
domains equally well (it surely does not), but that developers value the
```
Fix applied.
> "The entire reason I use Go is the great tooling and standard library. I'm```suggestion
> "The entire reason I use Go is the great tooling and standard library. I'm
```
Fix applied.
Unfortunately embedded use cases were left off of the revised list, but we'll```suggestion
Unfortunately, embedded use cases were left off the revised list, but we'll
```
Fix applied.
than other toilsome tasks, though we don't yet have strong understanding of```suggestion
than other toilsome tasks, though we don't yet have a strong understanding of
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
codebases or projects. One way to alleviate this additional load is clear,Perhaps this should be a colon?
Done
Should there be a period at the end of this sentence?
Thanks for catching this! That was an unfinished sentence :)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
LGTM (can't find any more easily spotted typos)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |