On Sun, Jan 29, 2023 at 7:34 PM Diego Augusto Molina <
diegoaugustomol...@gmail.com> wrote:
> From times to times I write a scraper or some other tool that would
> authenticate to a service and then use the auth result to do stuff
> concurrently. But when auth expires, I need to synchronize all
>From times to times I write a scraper or some other tool that would
authenticate to a service and then use the auth result to do stuff
concurrently. But when auth expires, I need to synchronize all my
goroutines and have a single one do the re-auth process, check the status,
etc. and then
Are the std/runtime .so's even versioned? How do you manage that?
Every time I'm feeling like finally being in $PARADISE out of the .so
dependency $VERYVERYHOTPLACE there comes along the demand to go back. Sigh.
;)
On Sunday, January 29, 2023 at 9:26:51 PM UTC+1 bobj...@gmail.com wrote:
>
I'm glad to see this issue getting some discussion. I have 100+ smallish
utility programs written in Go, and each one consumes about 1.5 MB (precise
average: 1,867,844 bytes); my bin directory contains 100+ copies of the Go
runtime. Sadly, I mainly use Windows, and there seems to be no way to
The discussion of SSD wear and tear is going way off my original question.
I'm sorry I even mentioned it.
Can we drop it?
I'm still interested in the answer to the original question, which we've
made some progress in answering.
As of now the answer is yes, subject to some permission and
This is pretty OT, and I am no expert, but the overwhelming consensus on
the inter-tubes seems to be that *reading *from an SSD causes no 'wear'
whatsoever. It is only writes and deletes that age an SSD. So this use case
should not impact SSD life.
But it is an interesting endeavor on its
