Live data from Hacker News

Go 1.24's go tool is one of the best additions to the ecosystem in years

jvt.me

1–10 of 207 posts

Re: Go 1.24's go tool is one of the best additions to the ecosystem in years

#2
As someone who’s been using Go since 2013 at commpanies like Apple, Microsoft, and Uber, this all seems quite unnecessary.

That said, if it helps people do “their thing” in what they believe is an easier (more straightforward) way, then I welcome the new changes.

Re: Go 1.24's go tool is one of the best additions to the ecosystem in years

#5

As someone who’s been using Go since 2013 at commpanies like Apple, Microsoft, and Uber, this all seems quite unnecessary. That said, if it helps people do “their thing” in what they believe is an easier (more straightforward) way, then I welcome the new changes.

Given Go’s approach to “metaprogramming” has long relied on tools written in Go, this does seem like a feature gap that needed closing. Even the introduction of `go generate` long ago formalized this approach, but still left installing the tools as an exercise for the reader. You can’t have consistent code gen if you don’t have consistent tooling across a team/CI.

Re: Go 1.24's go tool is one of the best additions to the ecosystem in years

#7
post #3

I have tested it and probably will use it but the fact that it pollutes your go.mod's indirect dependency list (without any distinction indicating it's for a tool) is very annoying.

Yeah, I'm still rather excited about it, but less-so given it /does/ impact the `go.mod` for consumers

Re: Go 1.24's go tool is one of the best additions to the ecosystem in years

#10
This seems handy, but often the tools run by `go generate` are outside of the Go ecosystem, or need to be binaries.

So I think a general solution would work better, and not be limited to Go. There are plenty of tools in this space to choose from: mise, devenv, Nix, Hermit, etc.

Post reply on HN