golang.org Packages random sorting?

<p><a href="https://golang.org/pkg/">https://golang.org/pkg/</a> docs is inconsistent in package order. And I don&#39;t think it&#39;s an April fools gag -- noticed it days, if not weeks ago.</p> <p>for example, loading the page I get (ignoring sub-packages):</p> <ol> <li>archive</li> <li>builtin</li> <li>compress</li> <li>...</li> </ol> <p>then after a few page reloads:</p> <ol> <li>archive</li> <li>bytes</li> <li>database</li> <li>...</li> </ol> <p>anyone else see the same?</p> <hr/>**评论：**<br/><br/>sh41: <pre><p>This was a regression that has been recently resolved. See issue <a href="https://golang.org/issue/24601" rel="nofollow">#24601</a>.</p> <p>Note that while it&#39;s been fixed in source, <a href="https://golang.org/pkg/" rel="nofollow">https://golang.org/pkg/</a> won&#39;t be updated until a version of Go is released. In the meantime, you can use <a href="https://tip.golang.org/pkg/" rel="nofollow">https://tip.golang.org/pkg/</a> or <a href="https://godoc.org/-/go" rel="nofollow">https://godoc.org/-/go</a> where the issue isn&#39;t present.</p></pre>itachi_amaterasu: <pre><p>Yep, I just fixed it yesterday. We will be re-deploying godoc soon (I am not sure of the actual policy of whether we need to bump Go version or not for a tools package change). In the meanwhile, you can use tip.golang.org.</p></pre>soapysops: <pre><p>I see that too. Maybe an old cached page or something haha.</p></pre>pdffs: <pre><p>If it&#39;s generated dynamically using a map or some concurrent tree walking, order won&#39;t be consistent. It could certainly be sorted in this case, at the cost of performance.</p></pre>