godevcontainer VS rosarygen

Installing the Go extension in VScode should prompt you to install what's needed. Otherwise you can use https://github.com/qdm12/godevcontainer ;)

If you have Docker installed and use VScode, you could try https://github.com/qdm12/godevcontainer which sets up your dev environment in a container so it's more reproducible.

I am the maintainer of godevcontainer which is a VSCode development container for Go.

VSCode + Docker using my image https://github.com/qdm12/godevcontainer will make your setup easy and reproducible for Go. I use it everywhere all the time.

If you have Docker installed and VScode you could use my development container qmcgaw/godevcontainer, I use it for every of my Go projects pretty much and it's sort of portable.

Jokes aside, yeah I do develop code for about everything inside development container (example)

Although I thought part 3 would be about dockerizing your Go dev environment, as in your workspace. I made and maintain godevcontainer to do that with Docker and use it all the time, for anyone curious.

Plus you can run your dev environment in a container (or remotely on a machine over ssh) which isn't really the case for Intellij. I use https://github.com/qdm12/godevcontainer with vscode.

I think that my so-far mostly unreleased audio package did this (you can see an early version of it as processor.go in https://github.com/TheGrum/rosarygen/blob/master/processor.go). It, and the similarly structured and also unreleased OpenStreetMaps query replayer I built compose flows, creating goroutines and channels as a matter of course in constructing flows that can run in parallel. It allows my audio stack to create flows that split and rejoin - be that treating left/right channels differently, or splitting into the complex realm with an FFT, or splitting into high-pass and low-pass or finer grained frequency-band streams, or mixing in multiple files. For the OSM query engine, it allows it to process a file, and pass location queries through to Nominatim to get a region, and then fire off a series of requests for that region at different zoom levels, while all those requests are fed to the OSM engine in a separate goroutine, along with more explicit requests coming from lat/lon specified ranges.