Our great sponsors
-
-
groupcache
groupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
> the ban prevents me from discussing the matter further
Hi ddevault, FWIW, in May 2022 on that #44577 issue [0] you had opened, it looks like someone on the core Go team commented there [1] recommending that you email the golang-dev mailing list or email them directly.
Separately, it looks like in July 2022, in one of the issues tracking the new friendlier -reuse flag, there was a mention [2] of the #44577 issue you had opened. In the normal course, that would have triggered an automatic update on your #44577 issue... but because that #44577 issue had been locked by one of the community gardeners as "too heated", that automatic update didn't happen.
Of course, communication on large / sprawling open source projects is never quite perfect, but that's a little extra color...
[0] https://github.com/golang/go/issues/44577
[1] https://github.com/golang/go/issues/44577#issuecomment-11378...
[2] https://github.com/golang/go/issues/53644#issuecomment-11751...
I remember one of the first real-world uses of Go being the groupcache package: https://github.com/golang/groupcache (to serve Chrome downloads, IIRC?)
> comes with a cache filling mechanism. Whereas memcached just says "Sorry, cache miss", often resulting in a thundering herd of database (or whatever) loads from an unbounded number of clients (which has resulted in several fun outages), groupcache coordinates cache fills such that only one load in one process of an entire replicated set of processes populates the cache, then multiplexes the loaded value to all callers.
If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...