5 ms·
> I resisted the recommended workspace configuration, as described in How to Write Go Code. Don’t bother, especially in the beginning I've had the same dev fol
by kasey_junk 11y ago
> I resisted the recommended workspace configuration, as described in How to Write Go Code. Don’t bother, especially in the beginning
I've had the same dev folder structure across platforms, languages, jobs and decades. I basically had to abandon that structure when starting Go. I fought & fought and at the end of the day it is just easier to use their expected workflow. It was (is?) galling but it was the only way to stop fighting the tools and get work done.
- XorNot 11y agoThe intellij go plugin is your friend. Per project go-paths. It's also a good use of make.