Here's one person trying to reduce binary bloat, while there's also a push to statically link everything. Who will win?
Alos, don't go rearranging the members of your structs if they're made public to third-parties!
Alos, don't go rearranging the members of your structs if they're made public to third-parties!
could you elaborate? who is pushing and what?
dynamic linking has it pitfalls, often it's a pain, but it has big big profits as well.
> could you elaborate? who is pushing and what?
I don't know of a more general movement, but Go developers seem very eager/proud about the single-binary thing. It can make deployments, particularly updates, much less issue prone.
Containers offer some tooling for resource management and such, though that is basically wrappers and other syntactic sugar dressing up OS facilities like resource groups so isn't anything you can't do with a statically linked binary too.