4 ms·

> You're making a big deal about "bought" but it doesn't really matter whether money changed hands. godoc.org existed, Google showed up, and now it does not. T

by rsc 5y ago

> You're making a big deal about "bought" but it doesn't really matter whether money changed hands. godoc.org existed, Google showed up, and now it does not. This is just as untrue as "Google bought just to cancel and replace with proprietary bloat...". We did not ask for godoc.org at all. The maintainer approached us to take it over, which we did, to keep an important service available to the Go community. Eventually we replaced it with a newer version of the service. The service still exists, it's just pkg.go.dev instead of godoc.org. The "proprietary" part is not true either, at least not anymore: the source code for pkg.go.dev is at golang.org/x/pkgsite. (It took us a couple months to get all the permissions lined up for the open source release, and that was a misstep on our part. There is a long story behind that, which I won't go into.) > The thing that replaced it is not functionally equivalent, full stop. I don't understand this comment. I see functionality on pkg.go.dev that is not available on godocs.io, like being able to see the version history of a package and look at docs for a particular version; annotations showing which version added a particular declaration to a package; detected license information; symbol search, like [http.Handler]; and reverse imports. I don't see any functionality on godocs.io that is missing from pkg.go.dev. Unless the comment is about not showing docs without a clear license permitting commercial use.

stonogo 5y ago
For those following along at home, "golang.org/x/pkgsite" redirects to "https://pkg.go.dev/golang.org/x/pkgsite https://pkg.go.dev/golang.org/x/pkgsite", which declares the repository to be at "https://cs.opensource.google/go/x/pkgsite https://cs.opensource.google/go/x/pkgsite", which gives a "Permission denied" error page unless you fetch code from Google Tag Manager. So it's all nicely open source, and not proprietary, as long as you subject yourself to Google's tracking mechanisms, or sign into your Google account, and do not license any libraries public domain -- Google will use them, but not show them to you. So as you can see, there's nothing to complain about, and we should all thank Google for their grandmotherly kindness.
- belak 5y ago
  It's also available as a mirror at https://github.com/golang/pkgsite https://github.com/golang/pkgsite. All the golang.org/x/* packages are thankfully available there, making them pretty easy to find.
preseinger 5y ago
pkg.go.dev provides a plainly worse user experience in many dimensions. It's more difficult to see the surface area of a package. It's more difficult to navigate between major versions of a given module. And there are numerous bugs on different browsers that aren't being fixed. The golang.org site provided no-frills but functionally excellent documentation which pkg.go.dev fails to match. The code behind pkg.go.dev is also plainly amateurish and buggy. It's a shame, really.
- philosopher1234 5y ago
  > It's more difficult to see the surface area of a package. It's more difficult to navigate between major versions of a given module. This is too vague for me to understand what you mean exactly. If I were rsc I would have no idea how to make you happy. The same goes for the rest of your comment, honestly.
  - preseinger 5y ago
    > This is too vague for me to understand what you mean exactly. When you go to a module's page on pkg.go.dev, the package documentation is hidden and requires a click to expand. The sections which enumerate the identifiers -- constants, functions, types, etc. -- are hidden by default and only become visible when you scroll to them. Major versions of a module are treated as distinct things rather than versions of the same thing. The navigation on the left-hand side breaks if the browser is less than some number of pixels.
akavel 5y ago
> I don't understand this comment. (...) I don't see any functionality on godocs.io that is missing from pkg.go.dev. Sorry, but: • Where can I access the diagram (not just a list) of the transitive imports graph of a package? • Quoting straight from https://golang.org/x/tools/cmd/godoc https://golang.org/x/tools/cmd/godoc, is the following functionality still present on pkg.go.dev? if yes, how can I access it? "For instance, https://golang.org/pkg/math/big/?m=all https://golang.org/pkg/math/big/?m=all shows the documentation for all (not just the exported) declarations of package big." And yes, I sometimes found it helpful when it was there. • Personally, when trying to search or browse the index of entities in a pkg.go.dev page, the auto-collapsing gives me trouble to get a good overview or quickly find stuff. I remember recently having to waste minutes trying to find something in the, of all the things, https://pkg.go.dev/std https://pkg.go.dev/std stdlib ToC, due to directories being auto-collapsed.

by rsc 5y ago

stonogo 5y ago

For those following along at home, "golang.org/x/pkgsite" redirects to "https://pkg.go.dev/golang.org/x/pkgsite https://pkg.go.dev/golang.org/x/pkgsite", which declares the repository to be at "https://cs.opensource.google/go/x/pkgsite https://cs.opensource.google/go/x/pkgsite", which gives a "Permission denied" error page unless you fetch code from Google Tag Manager. So it's all nicely open source, and not proprietary, as long as you subject yourself to Google's tracking mechanisms, or sign into your Google account, and do not license any libraries public domain -- Google will use them, but not show them to you. So as you can see, there's nothing to complain about, and we should all thank Google for their grandmotherly kindness.

belak 5y ago
It's also available as a mirror at https://github.com/golang/pkgsite https://github.com/golang/pkgsite. All the golang.org/x/* packages are thankfully available there, making them pretty easy to find.

preseinger 5y ago

pkg.go.dev provides a plainly worse user experience in many dimensions. It's more difficult to see the surface area of a package. It's more difficult to navigate between major versions of a given module. And there are numerous bugs on different browsers that aren't being fixed. The golang.org site provided no-frills but functionally excellent documentation which pkg.go.dev fails to match. The code behind pkg.go.dev is also plainly amateurish and buggy. It's a shame, really.

philosopher1234 5y ago
> It's more difficult to see the surface area of a package. It's more difficult to navigate between major versions of a given module. This is too vague for me to understand what you mean exactly. If I were rsc I would have no idea how to make you happy. The same goes for the rest of your comment, honestly.
- preseinger 5y ago
  > This is too vague for me to understand what you mean exactly. When you go to a module's page on pkg.go.dev, the package documentation is hidden and requires a click to expand. The sections which enumerate the identifiers -- constants, functions, types, etc. -- are hidden by default and only become visible when you scroll to them. Major versions of a module are treated as distinct things rather than versions of the same thing. The navigation on the left-hand side breaks if the browser is less than some number of pixels.

akavel 5y ago

> I don't understand this comment. (...) I don't see any functionality on godocs.io that is missing from pkg.go.dev. Sorry, but: • Where can I access the diagram (not just a list) of the transitive imports graph of a package? • Quoting straight from https://golang.org/x/tools/cmd/godoc https://golang.org/x/tools/cmd/godoc, is the following functionality still present on pkg.go.dev? if yes, how can I access it? "For instance, https://golang.org/pkg/math/big/?m=all https://golang.org/pkg/math/big/?m=all shows the documentation for all (not just the exported) declarations of package big." And yes, I sometimes found it helpful when it was there. • Personally, when trying to search or browse the index of entities in a pkg.go.dev page, the auto-collapsing gives me trouble to get a good overview or quickly find stuff. I remember recently having to waste minutes trying to find something in the, of all the things, https://pkg.go.dev/std https://pkg.go.dev/std stdlib ToC, due to directories being auto-collapsed.