Go 1.11 got me to stop ignoring Go
drewdevault.com
Go 1.11 got me to stop ignoring Go
1–10 of 79 posts
Re: Go 1.11 got me to stop ignoring Go
#2GOPATH issues - Elaborate more?
Re: Go 1.11 got me to stop ignoring Go
#3GOPATH issues - Elaborate more?
I was about to ask the same, then after some thinking about it, came to the conclusion that he doesn't like to be forced to save all Go libraries under $GOPATH. Now with Go 1.11 you can have "modules" that you can put all over the place. Much more freedom, right? :)
Re: Go 1.11 got me to stop ignoring Go
#4GOPATH issues - Elaborate more?
Apparently too lazy to set an environment variable. I found GOPATH annoying but not using Golang simply for that seems absurd to me.
Re: Go 1.11 got me to stop ignoring Go
#5GOPATH issues - Elaborate more?
Apparently too lazy to set an environment variable. I found GOPATH annoying but not using Golang simply for that seems absurd to me.
That's not the point: https://news.ycombinator.com/item?id=18178987
Re: Go 1.11 got me to stop ignoring Go
#6> I have major gripes with PEP-8, and if you ever see me using it I want you to shoot me in the face.
That sounds extreme. I've never heard this before. Why?
Re: Go 1.11 got me to stop ignoring Go
#7GOPATH issues - Elaborate more?
Apparently too lazy to set an environment variable. I found GOPATH annoying but not using Golang simply for that seems absurd to me.
You see, GOPATH crossed a line. Go is opinionated, which is fine, but with GOPATH its opinions extended beyond my Go work and into the rest of my system. As a naive new Go user, I was prepared to accept their opinions on faith - but only within their domain. I already have opinions about how to use my computer. I knew Go was cool, but it could be the second coming of Christ, and so long as it was annoying to use and didn’t integrate with my workflow, I (rightfully) wouldn’t care.
Re: Go 1.11 got me to stop ignoring Go
#8GOPATH issues - Elaborate more?
Go insists that all of your Go code must live inside of a single hierarchy under $GOPATH. This pretty much forces you to organise files in your system in a very particular way, where the language a project is written in takes precedence over any other organisational concerns, and doesn't play well with, e.g. my setup, where I file my projects in a hierarchy shaped like ~/dev/{personal,$COMPANY,3rdparty}/$PROJECT_NAME.
Re: Go 1.11 got me to stop ignoring Go
#9Earlier quoted context omitted.
Apparently too lazy to set an environment variable. I found GOPATH annoying but not using Golang simply for that seems absurd to me.
That's not the point: https://news.ycombinator.com/item?id=18178987
And just what point is that? The article states that "You see, GOPATH crossed a line. " Doesn't explain what that line is and then goes on to say that Golang is an awesome and simple language.
Re: Go 1.11 got me to stop ignoring Go
#10I guess go 1.11 introduced a modules experimental feature as an alternative to `GOPATH`
> Go 1.11 adds preliminary support for a new concept called “modules,” an alternative to GOPATH with integrated support for versioning and package distribution. Using modules, developers are no longer confined to working inside GOPATH, version dependency information is explicit yet lightweight, and builds are more reliable and reproducible. https://golang.org/doc/go1.11#modules