Live data from Hacker News

Go 1.15 Released

golang.org

21–30 of 74 posts

Re: Go 1.15 Released

#21

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?

Yes, I've had it happen. Not in subtle ways - usually a size check would show that something is very wrong anyway, but I appreciate the peace of mind. I usually like to bake a check into automation and had that catch things like the binary being replaced by a 404 page, etc... When I update the version I pull, I also update the checksum.

Re: Go 1.15 Released

#22
post #16

I think the link should be changed to the 1.15 release notes (now published): https://golang.org/doc/go1.15 -- these are much more interesting and useful.

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 machines where I need it. The production go versions only get updated as required.

Re: Go 1.15 Released

#25

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…

> I'm curious which package managers / repositories allow you to update to the latest version of go as soon as it's released * ?

Arch Linux.

I just saw the release when I was checking for updated versions of packages I maintain, and built it before users started bugging me about outdated go binaries.

https://www.archlinux.org/packages/community/x86_64/go/

Re: Go 1.15 Released

#26

"There are no changes to the language." Rob Pike is the ultimate troll.

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.

Re: Go 1.15 Released

#27
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?

Re: Go 1.15 Released

#28
> Changing the -timeout flag now invalidates cached test results. A cached result for a test run with a long timeout will no longer count as passing when go test is re-invoked with a short one.

I'm glad this is fixed! That will make life that one bit less annoying.

Re: Go 1.15 Released

#29
post #26

"There are no changes to the language." Rob Pike is the ultimate troll.

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.

His "I don't give a hoot" attitude to the people screaming "GO IS EVIL IT DOESN'T HAVE GENERICS" in the face of a decade of non-stop screaming is a testimony to how big his balls are.

Re: Go 1.15 Released

#30
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?

Given that modern systems include containerization and dozens or hundreds of instances of applications bouncing continually as changes are made or network conditions change, deployment has gotten a lot more “chatty” than tossing a binary on a server and running it.

Reducing binary size makes a difference when the app is deployed to remote servers thousands of times under normal operation.

Storage and bandwidth is cheap, yes, but it adds up.

Post reply on HN