Live data from Hacker News

Go 1.17 Release Notes

golang.org

11–20 of 222 posts

Re: Go 1.17 Release Notes

#11
My appreciation for Go has been monotonically increasing for years.

The more Go code I write, the more I like the language, the tools, and the standard library.

Low-friction, high-quality software development.

If only I could use it professionally, instead of C++.

Re: Go 1.17 Release Notes

#12
> Module authors may deprecate a module by adding a // Deprecated: comment to go.mod, then tagging a new version. go get now prints a warning if a module needed to build packages named on the command line is deprecated.

Very good for the ecosystem. Nudge folks to upgrade from broken/insecure versions

Re: Go 1.17 Release Notes

#13

It looks like the language is really maturing. The changes are all fairly minor optimizations and improvements to the stdlib. Impressed with the Go team’s discipline for simplicity and stability.

Between the 1 release in 2012 and the 1.13 release in 2019, this has been the development model of the language. So it's nothing new in Go's evolution.

Re: Go 1.17 Release Notes

#14
post #7

At first I didn't like Go because I thought it was too opinionated. But the more I used it, the more I found the tooling to be just heads and shoulders above similar languages like C/C++. I use VSCode a lot, and in VSCode you can press "F12" to jump to the location of a function definition. In Go I find myself deep diving into github libraries all the time just because F12 takes me there. That never happened with C/C…

If your reference point is C/C++ then sure.. Go is a progress, but give more modern languages a try, like Kotlin, they sure are a major ergonomic and featureful evolution over go

Re: Go 1.17 Release Notes

#15
Anyone seen jobs for business applications? Go seems to have a sweet spot for systems. I'd like to replace Java at my work but no one else is doing it.

Re: Go 1.17 Release Notes

#16
> We’ve also introduced pruned module graphs in this release. Modules that specify go 1.17 or higher in their go.mod file will have their module graphs include only the immediate dependencies of other Go 1.17 modules, not their full transitive dependencies.

This is a very welcome change and make the go.mod much more obvious to understand. Hooray!

Re: Go 1.17 Release Notes

#17

Golang release no longer excites me in a good way - I know my old aws hosted apps continue to work, as do my pet projects

are release notes supposed to be exciting?

I think they mean "no longer excites me, in a good way"

Re: Go 1.17 Release Notes

#18
post #15

Anyone seen jobs for business applications? Go seems to have a sweet spot for systems. I'd like to replace Java at my work but no one else is doing it.

When I used to work for traffic enforcement company, their whole backend was written in golang.

Re: Go 1.17 Release Notes

#19
post #9

Apparently type parameter compiler work was supposed to get merged just after 1.17. [1] Does anyone know if it’s still on? [1] https://groups.google.com/g/golang-dev/c/U7eW9i0cqmo/m/ffs0t...

The merge has already happened. The generic preview is going to be in 1.18 (early 2022).
Post reply on HN