赔偿多少？

轮询查询，只有查询到结果的时候，才出小票。
另外弱网问题要解决下，经常这样可不行。

写一套通用维护 token 的工具 /框架

使用方从这个框架 Get token 。

框架内部维护有效期，有个 goroutine 来将快过期的 token 续期。

之前有过类似想法，不过调研了一波国内的平台，均不支持外联或很有限，所以：环境不行，不够开放，做不起来。

rs4 瓦罐有很多人喜欢，但是相比来讲 rs5 掀背肯定更香。
不过具体来讲还是看个人喜好了，如果是我，选择 rs5

太棒！

为什么注册是个 about ？看起来像钓鱼的

考个？不可以买一个吗？那种野鸡大学

这公司还在呢？
之前和腾讯账号体系合并，就把账号丢了，后来又拆，早就弃用。

直接代码保持 1024 个字符宽不换行，还不用买显示器。

直接的健康吗现在没啥用了，都需要场所码，这样的话这个价值为 0

不要宝马 M ，你自己试驾一下就知道了，完全无趣，这个价格更不要考虑电动车。
可以看看 Audi RS5

这也太浅了？
面向后端技术么？

来自 rsc 的回复。

There are two problems with this GitHub repo:

it claims to host Go standards and does not, in the sense that these are in no way official standards
the project-layout standard it puts forth is far too complex and not a standard
Regarding "why not tell us the standard Go project layout and we'll update the doc?", that only addresses point 2. If there really were standards, they would be in the main Go project doc tree. The standard for project layout would also be a lot shorter. I appreciate your trying to provide a useful resource, but calling it 'golang-standards' is claiming more than it is.

But for the record, the minimal standard layout for an importable Go repo is really:

Put a LICENSE file in your root
Put a go.mod file in your root
Put Go code in your repo, in the root or organized into a directory tree as you see fit
That's it. That's the "standard".

In particular:

It is not required to put commands in cmd/.
It is not required to put packages in pkg/.
It is not required to put web stuff in web/.
It is not required to put APIs in api/.
It is not required to put web stuff in web/.
It is not required to put configurations in configs/.
It is not required to put systemd scripts in init/.
It is not required to put shell scripts in scripts/.
It is not required to put Docker files in build/package/.
It is not required to put CI configs in build/ci/.
It is not required to put deployment configs in deployments/.
It is not required to put test support in test/.
It is not required to put documentation in docs/.
It is not required to put supporting tools in tools/.
It is not required to put examples in examples/.
It is not required to put third_party code in third_party/.
It is not required to put git hooks in githooks/
It is not required to put static assets in assets/.
It is not required to put website data in website/.

The importable golang.org/x repos break every one of these "rules".

适合自己的就是最好的，也许某一种你认为“不好的”，比如关于 /pkg 的争论，当大家都这么做的时候，其实就是一种标准了。