HNHacker News
TopNewBestAskShowJobs

Mooby

-3 karma · joined December 17, 2012

submissionscomments
Mooby··on Thoughts on Go after a few days
So, when faced with criticism mentioned in the blog post and referred to in a post, instead of thinking about it you mindlessly insult others and say absolutely nothing about what has been said. Who exactly is the troll here?
Mooby··on Thoughts on Go after a few days
These are not source modules I'm talking about. If it was only necessary to set $GOPATH to point to source modules then everything would be fine. The problem is that go requires that $GOPATH points to a project's source tree to be able to build it, if the project is organized to store other go source files in subdirectories. We aren't talking about packages or modules intended to be reused in other programs. We are talking about how source code trees are organized.
Mooby··on Thoughts on Go after a few days
I'm not talking about gc. I'm talking about go. You know, the program which is extensively marketed as the only program which is required to build and run Go programs, and the standard and default way to deal with Go, from installing third-party packages and running your program through an interpreter.

Referring to gc makes as much sense as referring to gccgo.

Mooby··on Thoughts on Go after a few days
Supporting declaring variables with new(), make and local variable assignment isn't mandated by the need to make the grammar regular. It's simply a braindead idea. Go might have significant improvements over C, but they screwed the pooch on this one.
Mooby··on Thoughts on Go after a few days
That approach is nice and all if we are dealing with modules which we wish to reuse. If instead we would like to organize our source tree following a deep directory structure, we are forced to screw around with $GOPATH, which is a braindead idea.
Mooby··on Thoughts on Go after a few days
You started your post by claiming it wasn't true, but you proceeded to say that yes, it is in fact true.

As it is stated in the screencast, a programmer needs to add the workspace to $GOPATH to be able to build the source. That means that for each project being developed in Go, you need to add the path to that project to $GOPATH to be able to build it.

That is a very poor way to do develop software.

Mooby··on Thoughts on Go after a few days
He forgot to mention how programmers need to add each project directory to $GOPATH to be able to include files stored in project subdirectories. Talk about a braindead idea.