3 ms·
> No dynamic library linking: executable sizes in the range of several hundred megabytes I thought that with Golang and the popularity of static linking for ap
by nineteen999 9y ago
> No dynamic library linking: executable sizes in the range of several hundred megabytes
I thought that with Golang and the popularity of static linking for apps in Docker containers that this was now considered acceptable again (tongue firmly in cheek).
- std_throwaway 9y agoI don't actually see this as a problem; as long as you're only running one application like that.
- nineteen999 9y agoIf somebody is going to run statically linked binaries, they would understand the security implications of that, and that they need to be able to rebuild and redeploy their binary if a security hole is discovered in a third-party library that was linked into their program. They would already have CI/CD processes in place to rebuild the binary/container, run regression tests and redeploy the application/container to production, surely? So what difference does it make if it's one or one hundred applications/binaries/containers then?