The State of Go in 2026: Survey Data on AI Integration, Tooling Changes, and Developer Demographics

  • PublicPublic
  • 10 Nov, 2026
The State of Go in 2026: Survey Data on AI Integration, Tooling Changes, and Developer Demographics

The 2026 JetBrains Developer Ecosystem survey, conducted between May and July, gathered data from 28,945 developers, with 1,836 identifying Go as a primary language. Backend web development remains the dominant use case for 80% of Go developers, while command-line interface (CLI) utilities account for 49%. A significant trend is the growth of full-stack work, rising from 30% in 2025 to 40% in 2026. This shift correlates with TypeScript becoming the most common companion language, jumping from 24% in 2024 to 43% in 2026. In effect, a Go backend with a TypeScript frontend has become the default stack for many teams. Python (35%) and Java (22%) remain other common primary languages, but TypeScript's project-level integration has outpaced them.

Tooling preferences are shifting toward the standard library, driven by improvements in Go 1.22 and the rise of AI-assisted coding. The usage of net/http rose to 46%, nearly matching Gin at 48%, while chi, Echo, and Fiber hold smaller shares. The standard ServeMux now supports method matching and wildcards, reducing the need for third-party routers. Additionally, AI agents can handle boilerplate code, diminishing the advantage of frameworks like Gin that previously saved time on repetitive tasks. In testing, 35% of developers use no external frameworks, while Testify leads at 31% and GoMock at 25%. The share of developers not writing unit tests dropped to 14%, aided by AI tools that generate tests weekly for 84% of Go developers.

Go developers are heavily integrating AI into their workflows, particularly through command-line agents. 86% run AI agents in the CLI or terminal at least weekly, compared to 74% of all respondents. This preference persists even among senior developers with six or more years of experience, where 87% use CLI agents weekly. The Go toolchain, including go build, go vet, and go test, provides a fast, deterministic feedback loop that suits terminal-based agents. Despite this, IDE usage remains strong, with 61% of Go developers running coding agents inside their IDE daily. GoLand and VS Code are the most popular editors, each used by about half of Go developers, while Zed and Cursor also maintain significant shares.

The demographic profile of Go developers is characterized by high seniority and stability. 66% have six or more years of professional experience, compared to a 49% average across all respondents. Only 3% have less than a year of experience. This seniority correlates with higher salaries: 17% earn over USD 120,000 annually, and 9% earn more than USD 180,000. Most developers (70%) do not plan to migrate to another language within the next 12 months. Among those who do plan to learn new languages, Rust is the top choice, cited by 16% of Go developers. Rust usage in the last 12 months grew to 25%, indicating active adoption for performance-critical components rather than full rewrites of Go services.

Go developers maintain rigorous practices when reviewing AI-generated code. 79% review AI output often or always before acceptance, checking not only that it compiles but also for correctness, security, and maintainability. Most review occurs in the IDE (65%), followed by the AI agent interface (50%) and pull requests (42%). While 55% of Go developers report that more than 60% of their work code was fully generated by AI in the last month, they do not blindly trust it. 29% rate AI-generated solutions as worse than their own code, slightly higher than the general population. However, 33% believe AI will eventually take over coding entirely, reflecting a mix of heavy reliance and cautious skepticism regarding the quality and long-term impact of AI assistance.