gopls
No written verdict yet. Here is what commenters said.
6recommend
2warn against
Nov 15, 2025first mention
Aug 20, 2026latest mention
Why people recommend it
“I give my agent access to go pls and find it overall beneficial”
“gopls is a great LSP, though, and it warns you about this immediately.”
Show 3 more
“You can also get escape analysis visualizations in vscode via gopls”
“go build, go test, go fmt, gopls etc) which saves a lot of prompts and tokens”
“go fix, go vet, gopls - the stdlib toolchain does a lot that other ecosystems need third-party plugins for.”
Caveats and dissent
“I honestly laughed out loud the first time i used gopls.”
Who recommends it in their own words
From the makers not counted in the ranking
“since we enabled it over a year ago in gopls, our LSP server”
Threads where it came up
- Using go fix to modernize Go code 2 mentions
- Go 1.27 Is Released 1 mention
- Boris Cherny says "delete your Claude.md every 6 months" 1 mention
- Go Analysis Framework: modular static analysis by go team 1 mention
- Escape Analysis in Go: Stack vs. Heap Allocations Explained 1 mention
- Zig: Build System Reworked 1 mention
Data: gopls.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 12
I’ve been able to run golangci-lint locally just fine. However I’ve not had much success running it on CI, with at least the 1.27rcs. I encountered some panic deep within staticcheck, and ended up turning off that specific linter on CI (better than not running it at all). There was a tracking issue for go1.27 support at [1]. However that is now closed, which might imply that it should be working. [1] https://github.c
“I give my agent access to go pls and find it overall beneficial”
“gopls is a great LSP, though, and it warns you about this immediately.”
“You can also get escape analysis visualizations in vscode via gopls”
“I honestly laughed out loud the first time i used gopls.”
“A comparison between the performance of RLS / rust-analyzer (painfully slow) and gopls”
“I don't have to care a lot about gopls changes, because I rely on LSP protocol itself”
“go build, go test, go fmt, gopls etc) which saves a lot of prompts and tokens”
“For go, I used this on my lsp settings and it worked great.”
I believe go tooling is one of the top loved features among gophers, in particular gofmt. The best part is that all those command line utilities are also available for import. I've used them to create a license checker by walking the dep tree in code. There are also a ton of gems in the `./internal` directories, Roger Peppe has extracted them for reuse here: https://github.com/rogpeppe/go-internal
“go fix, go vet, gopls - the stdlib toolchain does a lot that other ecosystems need third-party plugins for.”
“but now Go users get a limited form of opt-in LSC support whenever modernizers make a suggestion.”