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 use linked libraries in Go for Windows.
My solution has been to rewrite many of my smallish Go programs in Python (except those that really need Go's speed) -- 10K each vs. 1.5M each disk storage. For these manually invoked utilities, the speed difference is often not noticeable. And the number of source lines and overall program complexity is reduced by roughly 30%. (Added benefit: the Python programs are always properly indented, even without a "pyfmt" program :-) I *am* a Go fan, and I understand that Go's mission is for writing big server programs, but it's too bad that the size of a small Go program executable is *many* times larger than a small C program. On Sunday, January 29, 2023 at 9:49:17 AM UTC-8 jlfo...@berkeley.edu wrote: > 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 performance > problems. I hope the experts > can shed some light on these. > > Cordially, > Jon Forrest > > -- 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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/3c691095-e0d8-4da5-8513-887af7b0e9b4n%40googlegroups.com.
