4 ms·
The container revolution appears to have come full circle and reinvented static linking.
by zbentley 8y ago
The container revolution appears to have come full circle and reinvented static linking.
- markbnj 8y agoWhich language produces statically linked binaries that embed their own root filesystem?
- groestl 8y agoThe question is: which languages _require_ their own root filesystem. Because all of them can join the single executable party now too.
- rkeene2 8y agoTcl.
- TheDong 8y agoSmalltalk, which distributes code as a vm. Java jars aren't far off from having their own rootfs included along with the compiled class files.
- groestl 8y agoYepp, almost there. I'm still waiting for some mechanism to statically link a distributed binary, so we can get rid of kubernetes too.
- wpietri 8y agoIf it takes a container to get static linking for dynamic languages, that's fine by me. I have one Python project where I'm just using Docker to produce a single, self-contained lump so I don't have to fuck around when installing. This would be a step forward for me. And then I have a Python library and command-line tool [1] where an awful lot of the issues people report are library version nonsense. I tried to help the first few, but at this point I've decided it's just not my job to make up for the Python community's packaging issues and/or issues related to other open-source projects and OSes. I'd love to be able to produce the equivalent of a statically linked binary for those people. [1] https://github.com/wpietri/sucks https://github.com/wpietri/sucks
- preston4tw 8y agoThis may be of interest to you: https://www.pyinstaller.org/ https://www.pyinstaller.org/
- peterwwillis 8y agoStatic linking doesn't give you a sandbox