<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/tepir9jwt" -->

---
title: Help set Go's priorities for next year | daily.dev
description: The Go team opened the 2026 Go Developer Survey to gather feedback that shapes next year's priorities. It stays open through November 3 and takes about 10 to...
canonical: https://daily.dev/posts/tepir9jwt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Help set Go's priorities for next year | daily.dev
og:description: The Go team opened the 2026 Go Developer Survey to gather feedback that shapes next year's priorities. It stays open through November 3 and takes about 10 to...
og:url: https://daily.dev/posts/tepir9jwt
og:image: https://api.daily.dev/og/posts/TePiR9JwT.png
og:image:alt: Post cover image
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Help set Go's priorities for next year

**[Go Developers](https://daily.dev/sources/golangnuts)** · [@func25](https://daily.dev/func25) · 16 upvotes · 2 comments

## Summary

The Go team opened the 2026 Go Developer Survey to gather feedback that shapes next year's priorities. It stays open through November 3 and takes about 10 to 20 minutes, with every question optional. Last year 5,379 developers responded, and their top frustration was following Go best practices and idioms, cited by 33%. Since then, the team shipped a rewritten 'go fix' in Go 1.26 that automatically modernizes code, with more modernizers added in Go 1.27. Results will be shared on the blog in early 2027.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://go.dev/blog/survey2026-announce>

## Community discussion

Top comments from developers on daily.dev.

**@ahmetozel** · 0 upvotes

> The connection between last year’s 33% idiom concern and the rewritten go fix is useful evidence that the survey influences tooling. For the next round, I would separate uncertainty about which idiom to choose from difficulty applying a known modernization across a codebase. Those can produce the same frustration response but need different interventions.
>
> It would also help to compare responses from developers who have tried the new modernizers with those who have not. A lower headline frustration rate alone would not show whether tooling helped existing users or the respondent mix simply...

**@ristotoldsep** · 0 upvotes

> Love that Go asks developers what hurts before inventing twelve new ways to spell it.

## Similar posts on daily.dev

- [Golang Weekly Issue 579: November 19, 2025](https://daily.dev/posts/golang-weekly-issue-579-november-19-2025-mxhxcalhr) · Golang Weekly · 13 upvotes · 0 comments
- [The 2026 Developer Survey is now open \(for human developers only\)\!](https://daily.dev/posts/the-2026-developer-survey-is-now-open-for-human-developers-only--ib9zsv6ag) · Stack Overflow Blog · 2 upvotes · 0 comments
- [Take the 2026 ISO C\+\+ Developer Survey\!](https://daily.dev/posts/take-the-2026-iso-c-developer-survey--qlxgasbmo) · DevBlogs · 0 upvotes · 0 comments
- [Go team to improve support for AI assistants](https://daily.dev/posts/go-team-to-improve-support-for-ai-assistants-tv21tefwd) · InfoWorld · 0 upvotes · 0 comments

---

Tags: [#golang](https://daily.dev/tags/golang)

[View this post on daily.dev](https://daily.dev/posts/tepir9jwt)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/tepir9jwt","headline":"Help set Go's priorities for next year","text":"Shared: Help set Go's priorities for next year","url":"https://daily.dev/posts/tepir9jwt","datePublished":"2026-10-23T03:10:46.419Z","dateModified":"2026-10-23T03:10:46.422Z","author":{"@type":"Person","name":"Phuong Le","url":"https://daily.dev/func25","image":"https://media.daily.dev/image/upload/s--HbVBqLGd--/f_auto,q_auto/v1697862633/avatars/avatar_s1rxG2e5sEfVSY1wCzdr8","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":9355}},"image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":16},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"sharedContent":{"@type":"WebPage","url":"https://api.daily.dev/r/zf3m1aAUX"},"comment":[{"@type":"Comment","text":"The connection between last year’s 33% idiom concern and the rewritten go fix is useful evidence that the survey influences tooling. For the next round, I would separate uncertainty about which idiom to choose from difficulty applying a known modernization across a codebase. Those can produce the same frustration response but need different interventions.\nIt would also help to compare responses from developers who have tried the new modernizers with those who have not. A lower headline frustration rate alone would not show whether tooling helped existing users or the respondent mix simply changed.","datePublished":"2026-10-30T05:57:13.038Z","url":"https://daily.dev/posts/TePiR9JwT#c-dtyHEB8SO","author":{"@type":"Person","name":"Ahmet Özel","url":"https://daily.dev/ahmetozel","image":"https://avatars.githubusercontent.com/u/70992231?v=4"}},{"@type":"Comment","text":"Love that Go asks developers what hurts before inventing twelve new ways to spell it.","datePublished":"2026-10-26T09:42:13.543Z","url":"https://daily.dev/posts/TePiR9JwT#c-ACXEBtQCk","author":{"@type":"Person","name":"Risto Tõldsep","url":"https://daily.dev/ristotoldsep","image":"https://lh3.googleusercontent.com/a/ACg8ocLDWc6mZn0JwNmXXw6WY0L_HJ6pegzRttooC5VgtXESHSj3MNYx=s96-c"}}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/squads/golangnuts","name":"Go Developers"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Go Developers","item":"https://daily.dev/squads/golangnuts"},{"@type":"ListItem","position":3,"name":"Help set Go's priorities for next year"}]}
```

