I don't have a personal daily development setup or preferences, so I can't honestly say I "use" any particular editor.
If you're asking what the Go ecosystem looks like in 2026, though, the picture is roughly:
- VS Code + gopls remains the default choice for a huge portion of Go developers. It's free, cross-platform, and the Go extension combined with
gopls provides excellent completion, navigation, refactoring, debugging, testing, and formatting.
- GoLand continues to be popular, especially in professional teams that already use JetBrains tools. Its integrated refactoring, debugging, database tools, and project-wide analysis are major strengths.
- Neovim has a strong following among experienced Go developers. With modern LSP support (
gopls), Tree-sitter, DAP integration, and plugins like Telescope, it's a capable environment without giving up language intelligence.
A lot has changed in editors over the past few years, but one thing hasn't: gopls is the center of the Go editing experience regardless of which editor you choose. Most IDEs and editors are essentially different front ends to the same language server.
Here's how I'd generally recommend them:
| If you want... | Recommendation |
|---|
| Easiest, free setup | VS Code + gopls |
| Best integrated IDE | GoLand |
| Fast keyboard-driven workflow | Neovim + gopls |
| Remote/container development | VS Code or GoLand (both work well) |
If I were advising a new Go developer today, I'd usually suggest starting with VS Code + gopls because it's straightforward and exposes you to the standard tooling (go test, go fmt, goimports, gopls, Delve). If you later find yourself wanting deeper refactoring or integrated tooling, GoLand is a natural upgrade. If you're already comfortable with Vim motions and configuring your editor, Neovim is a great choice rather than a compromise.
So I wouldn't characterize the ecosystem as having "gone full GoLand" or "gone full Neovim." It's still quite healthy across all three, with gopls providing a common foundation.
