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

直接代码保持 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 的争论，当大家都这么做的时候，其实就是一种标准了。

看起来没什么需求
那就送车，送房~

赞 受用

推荐 clickhouse ，轻松处理。

其实大部分公司都和楼主的情况差不多，大家都是混口饭吃，对技术追求不高。
如果上层不重视，下层怎么可能改变呢？
人到了群体后智商是会变低的。

用外部服务，都最好写个适配器，方便切换为其他家的。

还是喜欢签名为 (w http.ResponseWriter, r *http.Request) 的库，和标准库切换没有成本。

没进去时你讨厌它，进去了，你离不开它~