4 ms·
If you don't have a pipeline to update those static binaries, you're just giving yourself a different form of headache 5 years from now when you need to apply
by yjftsjthsd-h 6y ago
If you don't have a pipeline to update those static binaries, you're just giving yourself a different form of headache 5 years from now when you need to apply bug fix.
- lanstin 6y agoWith static linking you mostly have all the pieces updatable independently. Can move to new distro and keep the binaries. Can update some binaries with a bug fix to some parser library without releasing other binaries. Etc. except for glibc and stuff like 64-bit inode values.
- busterarm 6y agoThat's not a deployment problem though. And if everything you did to build those binaries failed, you can still run those binaries. You aren't out of business. We're talking about this versus the alternative of potentially not being able to deploy anything. Then you're dead. In both cases you needed a build pipeline anyway...unless you're operating in a world where "it works on my machine" is a good enough answer.
- jart 6y agoIf you like static binaries then you'll love this project: https://justine.lol/cosmopolitan/index.html https://justine.lol/cosmopolitan/index.html Here's an example of a 64kb statically linked binary that runs on all operating systems https://justine.lol/memzoom/index.html https://justine.lol/memzoom/index.html