Go for Visual Studio Code VS vim-go

There are a handful of really good go plugins that take care of this for you, such as https://github.com/ray-x/go.nvim or https://github.com/fatih/vim-go

With vim-go and snippets, neovim has almost the same functionality as GoLand

Neovim with its lsp integration. Yes, my configuration breaks whenever neovim is upgraded (it is < v1 after all). But usually I wait a little while, and then update plugins and I’m good to ‘go’. One very very good plug-in is https://github.com/fatih/vim-go. The wiki page has a suggested vimrc, which works very well to integrate things like identifier highlighting, and references.

with this wonderful plugin: https://github.com/fatih/vim-go

At first Ihad struggled with some common "IDE" tasks. But then I discovered vim-go and realized that it could do pretty much everything that I need and even more.

I use vim as an editor, and I think that vim-go (https://github.com/fatih/vim-go) is a huge help, if you use the "gd" shortcut to take you to where a variable, type or function is defined, and the ctrl-T shortcut to take you back. Use goimports (https://pkg.go.dev/golang.org/x/tools/cmd/goimports) as the vim-go code formatter. This will keep imports up-to-date. There are some other vim-go features that may be helpful. You can have it highlight syntax errors, for example. Not every feature is helpful to every programmer, however.

Maybe there's a reason why this isn't possible, but if I compare this work-flow with something like https://github.com/fatih/vim-go I can use go-to-definition for everything (whether it be a third-party package or a standard library feature such as fmt.Printf).