Live data from Hacker News

Go 1.15 Released

golang.org

61–70 of 74 posts

Re: Go 1.15 Released

#61
post #40

Earlier quoted context omitted.

I'm so confused by this. Given the context that Go primarily targets, which is daemon services running on server class machines, binary size, so long as it's not totally absurd, is almost completely irrelevant. Is it like a code golf thing? Why do you care?

These days, server-class machines are often ephemeral and spun up-and-down based on demand. At work, I operate services that have 2 GB of Java code packages, and others that use a single 10 MB Go binary. Guess which one can scale up much more quickly to handle increased demand?

Apparently it is time to learn how to use Java linker.

Re: Go 1.15 Released

#62

> The compiler's -json optimization logging now reports large (>= 128 byte) copies and includes explanations of escape analysis decisions. This sounds interesting.

I haven't found any more info about this feature. Anyone have better search skills than me?

Re: Go 1.15 Released

#63
post #24

Caddy binaries on Linux shrink by ~2.5 MB with Go 1.15! (~33 MB down to ~31 MB) 3 MB savings on Mac, and 2 MB on Windows: https://github.com/caddyserver/caddy/pull/3642#issuecomment-... So about 8-10% reduction.

I'm so confused by this. Given the context that Go primarily targets, which is daemon services running on server class machines, binary size, so long as it's not totally absurd, is almost completely irrelevant. Is it like a code golf thing? Why do you care?

I think the fact that binary size has become smaller rather than larger is notable in a world where most other software seems to be increasingly more resource hungry.

Re: Go 1.15 Released

#64
post #2

Where are signatures for these binaries published?

Source tarball: https://storage.googleapis.com/golang/go1.15.src.tar.gz Signature: https://storage.googleapis.com/golang/go1.15.src.tar.gz.asc Signed with `EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796` which is the Google Linux Packages Signing Authority. EDIT: I realized you wanted the binaries. You can fetch them from " https://dl.google.com/go/go1.15.linux-amd64.tar.gz.asc" , append `.asc` to the binary I reckon. Sign…

Thanks!

Strange decision not to link them from the download page.

Re: Go 1.15 Released

#65
post #26

Earlier quoted context omitted.

What do you mean? Go has been known for its philosophy of “Boring is Good”. Lots of releases these days come with either no changes to the language or some very minor ones.

> Boring is good. Until you reach channels and realize that mantra apparently went out the window at some point.

Can you elaborate? I'm asking because I've almost never had any issues with channels.

Re: Go 1.15 Released

#66
post #64

Earlier quoted context omitted.

Source tarball: https://storage.googleapis.com/golang/go1.15.src.tar.gz Signature: https://storage.googleapis.com/golang/go1.15.src.tar.gz.asc Signed with `EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796` which is the Google Linux Packages Signing Authority. EDIT: I realized you wanted the binaries. You can fetch them from " https://dl.google.com/go/go1.15.linux-amd64.tar.gz.asc" , append `.asc` to the binary I reckon. Sign…

Thanks! Strange decision not to link them from the download page.

Yes, I recently discovered there are signatures for the tarballs. I believe they where not added to the Arch Linux package because they are hidden.

Re: Go 1.15 Released

#67

Earlier quoted context omitted.

With very large, very important downloads, I also appreciate a quick check that no corruption or loss was involved in the download for benign reasons either.

Has this actually happened to someone in the last 10 years?

Yeah, I do remember having an unexpected broken download (via curl from memory) a few months ago. Didn't notice until trying to use the archive and things complained.

Re: Go 1.15 Released

#68

> The compiler's -json optimization logging now reports large (>= 128 byte) copies and includes explanations of escape analysis decisions. This sounds interesting.

I haven't found any more info about this feature. Anyone have better search skills than me?

As far as I understand, it's only about including more information in the compilers json output. But that information was already available in non-json output in previos Go versions.

To get explanations on the optimization decisions by the compiler build your package with:

    go build -gcflags="-m -m"
See also:

    go tool compile -h
    go doc cmd/compile

Re: Go 1.15 Released

#69

Earlier quoted context omitted.

Yes, I agree. No point on linking to the download page, most people use their package manager to update their Go installation.

I'm curious which package managers / repositories allow you to update to the latest version of go as soon as it's released * ? * In any remotely trustable and reliable way; random PPAs relying on somebody's free time don't count, IMHO. I've noticed Ubuntu, Debian, Centos, and Oracle Enterprise Linux are always trailing by quite a clip. Often years. The strategy I've been using is to just manually install it on the ma…

The snap distribution: https://snapcraft.io/go . The 1.15/stable channel is already up, and I expect the default latest/stable channel will switch in short order.

Re: Go 1.15 Released

#70
post #69

Earlier quoted context omitted.

I'm curious which package managers / repositories allow you to update to the latest version of go as soon as it's released * ? * In any remotely trustable and reliable way; random PPAs relying on somebody's free time don't count, IMHO. I've noticed Ubuntu, Debian, Centos, and Oracle Enterprise Linux are always trailing by quite a clip. Often years. The strategy I've been using is to just manually install it on the ma…

The snap distribution: https://snapcraft.io/go . The 1.15/stable channel is already up, and I expect the default latest/stable channel will switch in short order.

Snap is only good if you don't mind getting forced updates at any time, and no ability to pin versions without going to great lengths. You can't even control when the updates get installed. I avoid it like the plague.
Post reply on HN