Live data from Hacker News

Go 1.7 is released

blog.golang.org

1–10 of 141 posts

Re: Go 1.7 is released

#4
post #2

Seems like a great release. Faster compilation and faster at runtime. Normally these 2 are considered opposite of each other.

And smaller binary size too. For a statically linked blob, that's a big plus.

Re: Go 1.7 is released

#5
post #2

Seems like a great release. Faster compilation and faster at runtime. Normally these 2 are considered opposite of each other.

After the transition from C to Go of the gc toolchain there was a lot of potential in both areas. The SSA backend increased even more that potential. And there is still room for improvement, so future versions will be even better. But yes, it's a great release. Congrats to the team!

Re: Go 1.7 is released

#7
Great work, Go team!

Standout points in my opinion:

Overall performance improvements:

>> "We observed a 5–35% speedup across our benchmarks."

Decreased compile times and binary size:

>> "While these changes across the compiler toolchain are mostly invisible, users have observed a significant speedup in compile time and a reduction in binary size by as much as 20–30%."

Vendoring dependencies by default:

>> "...and in Go 1.7... the "vendor" behavior is always enabled"

Context package added to std lib:

>> "To make use of contexts within the standard library and to encourage more extensive use, the package has been moved from the x/net repository to the standard library as the context package."

Re: Go 1.7 is released

#8
vendor directories are no longer optional, which is nice.

Go get now update submodules... I'm honestly not sure what the current hack is for package management, but I assume people are still doing wrappers around go get to pin to commits/versions, (or else building your own repos for funsies), and I'm wondering if that breaks anything.

Re: Go 1.7 is released

#9
post #6

Cool. What's the plan for Go 8? What exciting features are up ahead?

SSA for all architectures, then delete the old compiler backend and optimize the frontend which can then assume an SSA backend and do less work. (Currently the frontend assumes a less-capable backend so has to do more work, which actually makes SSA slower)
Post reply on HN