Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
proposal: x/build/cmd/release: remove godoc for Go 1.13 #30029
I am skeptical about removing batteries like godoc from the go distribution.
If anything, I think we should be having discussions about what tools are missing from the go distribution, like goimports.
Maybe it's only me but I start the web server before starting my editor.
I preach about Go when ever I get a chance and one of the selling points is that all you need to do to get started is to install the binary, start the web server and all you need is there on your machine to start learning Go.
When having to use Java I download the API docs to always have it available. With Go it's so great to have everything in one package, while a
I'm all for removing clutter but I think easy access to the documentation should come with the binary. To me it's not clutter.
If it’s underused maybe it should be more prominent in the getting started section? Or maybe have
Just to see how long it takes I just downloaded the latest MacOS binary and it took me 8 seconds. I don't know how much I would save by loosing the web server but even if I had a slower connection I wouldn't consider a 4-5 minute download a long time.
But then again maybe I'm just old when considering a 4 minute download as "fast"... :)
@spagettikod Thanks for feedback.
One of the bigger motivations for making it available primarily via
When I talked about this issue with @ianthehat, he made a good point that we've only considered two extremes in this proposal so far: to include vs not include the
It would be a bigger change to design and implement (and should be a separate proposal), but perhaps a similar solution can provide a better experience to Go users (e.g., they can conveniently choose whether to have the
Thanks for considering my feedback @dmitshur!
I didn't realize that
I looked at the Google Cloud link but I don't see the difference between that and what you already get using
Anyway I don't mind the possibility of updating the docs provided in the release using