Modern day go project structure?


Modern day go project structure?

Hi everyone. So, I've been sticking with go for quite some time, but recent almost two years I mostly didn't touch it for particular reasons (mainly I'm working with python). But now I wan't to write some go code again and further improve my knowledges and skills. And I'm kinda curious whats changed, if changed actually, in terms of project structure and dependency management. 'Cause back in the days everyone used go get, $GOPATH and single folder with src/pkg/bin folders in it. So, where should I look at and whats the most idiomatic way to write go code nowadays?

Thanks in advance

Submitted February 01, 2017 at 11:36PM by free2use
via reddit http://ift.tt/2kS8716