Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A command-line weather app built using Elixir

github.com

Post reply on HN
Print view View original

11–20 of 67 posts

Re: A command-line weather app built using Elixir

#11

Post by laumars »

djm_ wrote: post #10
renekooi wrote: post #4

Another ASCII art weather (forecast) utility, but in Go: https://github.com/schachmat/wego

Can anyone explain why a dependency of this app is a "working Go environment"? I thought one of golang's selling points was the fact that it created a simple binary. As far as I can tell, the Go environment is simply being used as a cheap installer, is that correct?

Because he's sharing the source code rather than a compiled binary. It's no different to having make + gcc listed as a dependency for C++ code.

Re: A command-line weather app built using Elixir

#12

Post by [deleted] »

djm_ wrote: post #10
renekooi wrote: post #4

Another ASCII art weather (forecast) utility, but in Go: https://github.com/schachmat/wego

Can anyone explain why a dependency of this app is a "working Go environment"? I thought one of golang's selling points was the fact that it created a simple binary. As far as I can tell, the Go environment is simply being used as a cheap installer, is that correct?

[deleted]

Re: A command-line weather app built using Elixir

#14

Post by fit2rule »

djm_ wrote: post #10
renekooi wrote: post #4

Another ASCII art weather (forecast) utility, but in Go: https://github.com/schachmat/wego

Can anyone explain why a dependency of this app is a "working Go environment"? I thought one of golang's selling points was the fact that it created a simple binary. As far as I can tell, the Go environment is simply being used as a cheap installer, is that correct?

In my opinion its more like: Go comes with a package-management/install system onboard, and for every 'go install', there's a full copy of working sources which someone, some day, might consider reading and contributing to ..

So I think, at least as a go newbie, that its quite handy that pretty much every tool I might be interested in - because it was written in Go - comes with full sources onboard as a basic, starting-gate, expectation. At least, I am quite happy to be learning Go this way ..

Re: A command-line weather app built using Elixir

#15

Post by frou_dh »

laumars wrote: post #11
djm_ wrote: post #10

Earlier quoted context omitted.

Can anyone explain why a dependency of this app is a "working Go environment"? I thought one of golang's selling points was the fact that it created a simple binary. As far as I can tell, the Go environment is simply being used as a cheap installer, is that correct?

Because he's sharing the source code rather than a compiled binary. It's no different to having make + gcc listed as a dependency for C++ code.

Strictly there is a little hindrance for the non-gopher user because this won't work until they set up a Go workspace, i.e. decided where they want GOPATH to be, set that, and added $GOPATH/bin to PATH to have the executable be runnable.

    $ env -i $(which go) get github.com/schachmat/wego
    package github.com/schachmat/wego: cannot download, $GOPATH not set. For more details see: go help gopath

Re: A command-line weather app built using Elixir

#16

Post by laumars »

frou_dh wrote: post #15
laumars wrote: post #11

Earlier quoted context omitted.

Because he's sharing the source code rather than a compiled binary. It's no different to having make + gcc listed as a dependency for C++ code.

Strictly there is a little hindrance for the non-gopher user because this won't work until they set up a Go workspace, i.e. decided where they want GOPATH to be, set that, and added $GOPATH/bin to PATH to have the executable be runnable. $ env -i $(which go) get github.com/schachmat/wego package github.com/schachmat/wego: cannot download, $GOPATH not set. For more details see: go help gopath

Indeed, but that's a separate point. The question was why Go was listed as a dependency and my answer was because it's a source code repository.

Also, you left off GOROOT from your Go environment :)

Re: A command-line weather app built using Elixir

#17

Post by frou_dh »

laumars wrote: post #16
frou_dh wrote: post #15

Earlier quoted context omitted.

Strictly there is a little hindrance for the non-gopher user because this won't work until they set up a Go workspace, i.e. decided where they want GOPATH to be, set that, and added $GOPATH/bin to PATH to have the executable be runnable. $ env -i $(which go) get github.com/schachmat/wego package github.com/schachmat/wego: cannot download, $GOPATH not set. For more details see: go help gopath

Indeed, but that's a separate point. The question was why Go was listed as a dependency and my answer was because it's a source code repository. Also, you left off GOROOT from your Go environment :)

> The question was why Go was listed as a dependency

You may have read it that way but the question was explicitly referring to "working Go environment"

Post reply on HN