| > if you recall it came with a lot of "We have no idea why you need this" from Pike and friends The blog post and design document both authored by Rob Pike at the time[0] contains none of that sentiment. The closest approach comes from the blog post which states: > Go generate does nothing that couldn’t be done with Make or some other build mechanism, but it comes with the go tool—no extra installation required—and fits nicely into the Go ecosystem. This, taken alone, would seem to support “we have no idea why you need this,” until you read the hope from the design document: > It is hoped, however, that it may replace many existing uses of make(1) in the Go repo at least. These are not words of someone who doesn’t understand why users would need this. Also, I am at a FAANG and my experience differs from the parent—`go tool` is sorely needed by my teams. [0] https://go.dev/blog/generate [1] https://go.googlesource.com/proposal/+/refs/heads/master/des... |