Two counterpoints: 1. Ian answered this last week: if there is something to say, say it here rather than leading a thread with a link to an blog post. That norm shouldn't change based on if an individual subscriber get value out of a given post. Anyone who wants every article can subscribe to get posts emailed from Medium.
2. Writing a decent post used to take hours or days which kept the volume self-limiting. It now takes ~30 minutes. I considered sending my blog posts to the list a while back but thought it would be bad netiquette. If weekly link-drops are fine, will it still be fine if a lot more of us do the same? -Mike P.S. My personal objection is to AI-written content, not occasional human-authored posts. P.P.S. I put my objection on the record now, so I don't plan to comment again on this topic. > On Jul 26, 2026, at 9:08 PM, Jason E. Aten <[email protected]> wrote: > > Nah. To me, these are fine. They are both topical to Go and discuss novel > aspects of Go programming, and are written fairly infrequently. I for one > appreciate them and have learned about important topics like eBPF from them. > They seems like appropriate use of go-nuts to me. > > I could wish the articles didn't use AI without fact checking... but meh, > humans make plenty of mistakes too. > > On Sunday, July 26, 2026 at 6:42:25 AM UTC-3 Duncan Harris wrote: > I think you probably need to stop posting these articles to this group. It is > not scalable. People will get annoyed. > > On Friday, 24 July 2026 at 23:02:37 UTC+1 Cheikh Seck wrote: > Go 1.26's runtime/secret (GOEXPERIMENT=runtimesecret) tags allocations inside > secret.Do(f) for erasure — the right layer to stop secrets leaking into crash > core dumps. Key takeaway: it marks, doesn't wipe — you must call runtime.GC() > right after or you still leak, and it's a no-op off linux/amd64+arm64. > > I built a reproducible harness (canary → SIGSEGV → scan the core): control > leaks, secret doesn't. Repo + Dockerfile: > https://github.com/cheikh2shift/go-snippets/tree/main/secret-demo > > Writeup: > https://towardsdev.com/runtime-secret-go-1-26s-answer-to-secrets-leaking-in-core-dumps-d884615e971f > > > -- -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/F2D6B184-B8A6-4420-A9CB-56733E20904F%40newclarity.net.
