> Unlike other languages where you can just create a directory and get started, Go wants you to put things in $GOPATH.<p>I've seen this complaint a lot and don't agree with it. Go just want everything to be accessible through $GOPATH, it doesn't have to _be_ there. Here's how I organize my code:<p>- I have all my dev in ~/dev. Anything goes here, whether it's go, ruby,... it's my workspace<p>- I put $GOPATH where it should be, in ~/.local/share/go<p>- Whenever I need to go get something, it ends up in ~/.local/share/go/src/domain.com/author/package, as expected<p>- When I need my package to be in $GOPATH, I just symlink ~/dev/project to ~/.local/share/go/src/github.com/rakoo/project, so it is visible in $GOPATH<p>After that everything works as expected (modulo some minor quirks I have to do at go install time), and you don't have to have a specific workspace just for go. It's also minimal enough (once per new project) that I'm not too bothered by it.
To me that criticism you quoted seems really misguided. A person who doesn't want to see performance measures from new users will never understand how they (the new users) are typically using the language and where the most common performance blocks are at the newbie stage.
>In a way, I consider that to be an advantage coming in to a new programming language, in that I have no preconceived notion of how things “SHOULD” be. <i>I can learn the language and use the constructs as they were intended, and not have to question WHY it was designed that way because it’s different than what I know.</i><p>>I just <i>could not get my non-functional mind to wrap around the functional Scala</i>. And since I really didn’t need to code (nor the developers want me to), <i>I gave up on learning Scala.</i><p>>I’ve barely heard of generics, communicating sequential processes, and other <i>“cool”</i> and <i>“advanced”</i> concepts.<p>Emphasis added
"For me personally, I don’t know any better. I have never used generics and I haven’t found a situation where I strongly require it."<p>Sounds an awful lot like <a href="http://c2.com/cgi/wiki?BlubParadox" rel="nofollow">http://c2.com/cgi/wiki?BlubParadox</a>
"I haven’t used this extensively, but in my attempt to optimize the integer compression library, I added different C and assembly snippets to try to squeeze the last ounce of performance out of Go. It was fairly easy and straightforward to do."<p>Ah, the famous integer compression library modifying non-programmer :)