<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>saturn_vk</author><text>Its almost exactly the same as gradle java projects. Each module there has a &amp;#x27;src&amp;#x27; directory where all code and whatnot lives. And nothing&amp;#x27;s stopping you from having a one-liner bash script that sets up the base as the GOPATH and then running `go build`&amp;#x2F;</text><parent_chain><item><author>bschwindHN</author><text>It&amp;#x27;s opinionated, and not the good kind. Some people like having simply a `projects` directory with &lt;i&gt;all&lt;/i&gt; coding projects inside. For almost any language, I can clone into this directory and run the associated build scripts. But Go has to be special and use a &lt;i&gt;special&lt;/i&gt; directory or else it throws a hissy fit.&lt;p&gt;Aside from that, I do enjoy the language a fair amount.</text></item><item><author>thewhitetulip</author><text>If you mean the $GOPATH directory notation, then I beg to differ, it is one of the favorite things about Go for me, because it is the repo which has all my Go code.&lt;p&gt;For other languages I have a `code` folder which has individual language folders and it contains project. Go has it by default.</text></item><item><author>deallocator</author><text>I must admit I was kind of hoping they&amp;#x27;d fixed their horrible requirements for your directory structure, interesting article nonetheless</text></item></parent_chain></comment><story><title>Looking at your program’s structure in Go 1.7</title><url>https://pauladamsmith.com/blog/2016/08/go-1.7-ssa.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>gernest</author><text>You can make a sub directory of your `projects`  your GOPATH.&lt;p&gt;Something like `projects&amp;#x2F;go`&lt;p&gt;I have multiple GOPATH for personal reasons and use long running tmux sessions which exports the different GOPATH.</text><parent_chain><item><author>bschwindHN</author><text>It&amp;#x27;s opinionated, and not the good kind. Some people like having simply a `projects` directory with &lt;i&gt;all&lt;/i&gt; coding projects inside. For almost any language, I can clone into this directory and run the associated build scripts. But Go has to be special and use a &lt;i&gt;special&lt;/i&gt; directory or else it throws a hissy fit.&lt;p&gt;Aside from that, I do enjoy the language a fair amount.</text></item><item><author>thewhitetulip</author><text>If you mean the $GOPATH directory notation, then I beg to differ, it is one of the favorite things about Go for me, because it is the repo which has all my Go code.&lt;p&gt;For other languages I have a `code` folder which has individual language folders and it contains project. Go has it by default.</text></item><item><author>deallocator</author><text>I must admit I was kind of hoping they&amp;#x27;d fixed their horrible requirements for your directory structure, interesting article nonetheless</text></item></parent_chain></comment><story><title>Looking at your program’s structure in Go 1.7</title><url>https://pauladamsmith.com/blog/2016/08/go-1.7-ssa.html</url></story>