Yes I mostly agree. Also I suspect a lot of the Go executable size comes from "initial" runtime overhead that does not scale linearly with the project size. R

Yes I mostly agree. Also I suspect a lot of the Go executable size comes from "initial" runtime overhead that does not scale linearly with the project size. Rapid scaling in a "Superbowl ad" or similar situation is affected heavily by cold boot time, which, as you point out, is a result of many factors, including your platform. If you use something like Lambda, your bundle size plays a much bigger role than if you fire up a new EC2 instance.