

I need to be able to develop with VSCode on a local codebase (to reuse Git credentials mainly) but the code should run on a Docker Compose development stack with lots of moving parts. Should you also want hot reloading (which you do when using Docker, otherwise you need to stop/restart containers and the debug session manually on every change).īefore getting hands-on, I'll go over my use case and what makes it a bit different. If you're developing in/for containers though, it gets a bit more complicated. If you're working locally, using Go's top debug tool (Delve) is straightforward. I'd rather pay a more moderate amount for the Go VSCode extension.īetween the Docker extension, the Remote Docker (which allows you the use of a container as if it were a local environment) and official Go extension (that also brings you all the Go tooling if you don't already have that) the development experience is top notch. Sure, Golang is great in itself but there's little there to justify the EUR 200 price for a year.

I have to say that Visual Studio Code, for all its pros and cons for various language, it's a totally awesome IDE for Go.
