Also, this isn't quite correct:
> There is also the approach taken by Go, which isn’t able to generate small applications like C, but instead incorporates a “runtime” into each packaged application. This approach is a compromise between Python and C, still requiring tens of megabytes for a binary, but providing for easier deployment than Python.
Compiling Go with gccgo instead of the Go compiler, and with the right flags, results in a much smaller executable.
It is also possible to further compress the executable with upx.
This command should result in executables around 0.5 to 1.5 MiB in size, on Linux (depending on the size of the Go project):
go build -mod=vendor -gccgoflags '-Os -s' -o prog && upx --best --lzma prog