Closed OneOfOne closed 5 years ago
I fully agree that the binary sizes are large measured by current web standards. So far, binary size hasn't been one of the main concerns of Go due to the main use cases it currently has. With WebAssembly this changes and we will see how much influence this will have on Go in the future.
Also please always look at the size difference with gzip applied, since this is the only size that really matters. With gzip, a quick experiment shows for me a difference of 1.1MB non-gzipped, but only 230KB gzipped.
For memory related issues see #27462
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputThis isn't a bug per-se, but I think maybe something can be done to improve that.
Feel free to close it or keep it as a reminder for later.