3 ms·
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 navigat
by 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.